Releases: polydawn/hroot
v0.5.3
A full set of changes can be found here.
Highlights:
- Updated compatibility to docker 0.11.1.
- Fixed a mounting error with relative folders.
- Added more debugging information when the
DEBUG=1environment variable is set.
Upgrading:
- Hroot is now designed to interoperate with docker 0.11.1, and unofficially 0.10.x.
- This is likely a backwards-incompatible change, as docker's API has changed again.
- If you're not ready to upgrade, stick with the previous release of Hroot, which uses docker 0.7.2.
Other comments:
The DEBUG=1 environment variable now prints a lot more information, with the intention of troubleshooting remote user's problems or issues with docker interactions. This can be rather verbose.
For now, the old debug behaviour (simply printing a stack trace on crash) has been changed to a DEBUG_STACK=1 environment variable. In the future, we'd like to improve this with proper log-levels.
v0.5.2
A full set of changes can be found here.
Highlights:
- Added
-Hflag passthrough to connect to any docker daemon. - Hroot now cancels a build with a helpful message if your git config isn't ready to commit yet.
- Fixed a bug where Hroot could crash if the Docker cache was cold.
Upgrading:
- Hroot will no longer start its own Docker daemon; this behaviour was confusing and would generally trigger when something else wasn't working.
v0.5.1
v0.5.0
v0.4.0
A full set of changes can be found here.
Highlights:
- New documentation with a tutorial to help new users get started.
- The configuration file syntax has been split into sections! Much easier to understand.
- Massive improvements to the way Docket interacts with your graph.
- Operations involving git should now be faster, smoother, and less surprising.
- Docket now attempts to use the system default daemon (in
/var/run) by default. - Cache detection was improved - no more loading from the graph unnecessarily.
- Updated to Golang 1.2.
Upgrading:
- The graph now uses the consistent branch prefix
docket/image/.- You will need to rename your branches accordingly.
- Additionally, Docket v0.4.0 lays down the contract of each commit beginning with the image name.
- This will allow us to support loading a specific branch's commit in the future (see #7).
- Nothing is required right now, but for future compatibility it's advised you amend your commits.
- Configuration files are now called
docket.tomland have a new layout. - Docket no longer assumes a default command; failing to provide one will now exit with an error.
- The build flag
--noopis now less confusing and is no longer used for bootstrapping. - Docket will now unconditionally use the system default daemon if it is running, then falls back on old behavior (looking for a dock folder and/or starting a daemon itself). In the future a
-Hflag will be added to make this easier (see #28).
Other comments:
Building Docket now requires Golang 1.2 due to switching out our use of a forked tar library.
This change mirrors a decision already made upstream by Docker.
With several Docket subsystems now firming up rather nicely, we've added several unit tests.
These can be run with ./goad test.
v0.3.0
A full set of changes can be found here.
Highlights:
- Docket graphs now hold the container's files, not tar archives. See a diff of your entire system!
- Docket now checks if the docker cache has the image you're requesting. You can now be reasonably sure you will never pull from the docker index unless explicitly requested via
-s index. - Lots of bug fixes and code cleanup under the hood.
Upgrading:
- Because the graph format no longer uses tars, loading from & saving to an old graph will not work! We have not implemented a system to carry your graph forward; you will need to rebuild.
- Docket no longer assumes a default image name; failing to provide one will now exit with an error, rather than launching Ubuntu.
Other comments:
Please note that there's an inherent race condition in checking if the docker cache has an image; another docker client could delete the image between check & use, which would trigger an index pull from docker. We have little control over this :(
This will be documented and possibly prevented further. For now, users in sensitive environments should still consider the standard /etc/hosts rule to block index.docker.io.