Repository navigation
fix insecure parameter - #591
Merged
Merged
Conversation
npeters
force-pushed
the
fix-insecure-registry
branch
from
October 27, 2014 22:51
67ba6a4 to
3cb3aeb
Compare
Signed-off-by: Nicolas Peters <[email protected]>
npeters
force-pushed
the
fix-insecure-registry
branch
from
October 27, 2014 23:06
3cb3aeb to
b64ea85
Compare
|
Thanks for this! I'm guessing recreate tries to pull the container if you've changed the image name. Is this right? |
Author
|
yes,if image name change you have to recreate all. |
|
LGTM |
yuval-k
pushed a commit
to yuval-k/compose
that referenced
this pull request
Apr 10, 2015
fix insecure parameter 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
3 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.
add to recreate_containers the parameter insecure_registry