docker-compose still ships from pypi

[Tim Van Steenburgh]

Opened by lazypower on 2016-12-13 14:49:17+00:00 at https://github.com/juju-solutions/layer-docker/issues/98

------------------------------------------------------------

docker-compose being pulled from pypi in exec.d/docker-compose/charm-pre-install.sh limits the offlineability of this charm.
Prior work was done to stuff docker-compose into the wheelhouse. That may still be a viable option for delivery of docker-compose from layer docker.

====================== COMMENTS ============================

Comment created by simonklb on 2017-06-29 11:57:33+00:00

Just encountered a bug when deploying my Docker charm due to it being introduced into docker-py. Fixing this issue would eliminate the risk of that happening again since you would at least stick with the version that your charm was built with and not pull the latest version at each deployment.

@chuckbutler would you mind putting some prio on this?

------------------------------------------------------------

Comment created by stub42 on 2018-08-03 08:06:08+00:00

~~This will affect CAAS charms, as it is recommended to use the docker layer.~~ All lies, as the docker-resource layer is recommended.