Merged
Conversation
Force using remote API version 1.14 so Fig is still compatible with Docker 1.2. Signed-off-by: Ben Firshman <[email protected]>
bfirsh
force-pushed
the
docker-py-0.6.0
branch
from
02b8a20 to
7887410
Compare
|
I was hoping we could do something like this #659 (comment) But I guess if there were minimal API changes, or fig doesn't need them, this option works as well. |
|
LGTM |
Author
|
I think we can add that separately: #719 |
yuval-k
pushed a commit
to yuval-k/compose
that referenced
this pull request
Apr 10, 2015
Upgrade to docker-py 0.6.0 Signed-off-by: Yuval Kohavi <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Force using remote API version 1.14 so Fig is still compatible with
Docker 1.2.
Signed-off-by: Ben Firshman [email protected]