Docker-Engine release

Moved to tracking the 'docker-engine' package from the archives instead of lxc-docker

This release also has the benefit of moving from device-mapper backend storage (not recommended) to AUFS by default. This yields in faster performance, and reduced disk usage for container fs layers.

Includes a fix from Gennady to properly restart the docker daemon during networking changes and corrects the ordering of ansible handlers! Thanks Gennady!

Various project meta cleanup relating to testing and having greens in CI.

Charm full of compose

Adds the compose option to the charm configuration. This allows you to deploy all the tooling necessary to launch complex container stacks on top of docker, without having to pip install anything yourself.

Combine this with the docker-compose-charm located here and you can launch an arbitrary docker-compose based stack out of any github repository.

Feedback welcome!

1.0 bugfixes

Bugfix release in relation to:

• Labels required key=value settings, this is now addressed in config-changed w/ setting the service name as the name key
• Refactored restarts to address random failures when standing up in the docker-core bundle
• Corrected a bug which caused first run failure when installing the new AnsibleCharm module not being on $PATH

v0.1.1: Correct some incoming bugs with relation to setting the docker_version

set_fact stanza

Adds a yaml= block when calling docker_opts

Developer Targeted Tooling

Release Notes

• Support for docker tagging enabled (prelim SWARM support)
• Docker Opts manager
• New Ansible charm support (breakout from charmhelpers)
• Updates to tests for testing version upgrade (no longer relies on metapackage)

v0.0.6: Change the nomenclature of the rendering statements in the playbook

Adds dockerpy + virtualenv to baseline install
Adds configurable option to set the version installed when latest=true
Patched a bug affecting empty template rendering during SDN network configuration
Adds stop hook to strip the core docker installation from the system during destroy-of-service cycle.