You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, because Flocker is already installed on these nodes, and because docker-py is a dep of flocker, docker-py is already installed too. And so, perhaps due to version number incongruity, the custom version of docker-py does not get pulled down (I think).
@binocarlos I saw this in manual testing, would you mind testing to confirm the issue exists?
WDYT about fixing this? We could just wait for a compose release that includes volume_driver support, although maybe adding a note to the docs in the meantime would help.
@lukemarsden Can confirm that this issue exists having tested it manually - once I had done the manual pip install step it did not complain about missing 'volume-driver' any more.
I'm not sure how we can specify a tighter dependency than a git commit hash?
I will put a note in the labs docs about these extra 2 steps I think that is the best plan until the change is merged into master.
we should update the compose docs to refer to the fact that mainline compose supports volume_driver now.
lukemarsden
changed the title
Compose install instructions don't work if you've installed Flocker
Compose install instructions are out of date [was: Compose install instructions don't work if you've installed Flocker]
Oct 6, 2015
Following the instructions here: https://docs.clusterhq.com/en/1.0.1/labs/compose.html
We are told to run:
However, because Flocker is already installed on these nodes, and because docker-py is a dep of flocker,
docker-py
is already installed too. And so, perhaps due to version number incongruity, the custom version ofdocker-py
does not get pulled down (I think).Manually running:
Resolves this issue.
The text was updated successfully, but these errors were encountered: