Remove ability to join bridge network + user-defined networks#2761
Merged
aanand merged 2 commits intodocker:masterfrom Jan 27, 2016
Merged
Remove ability to join bridge network + user-defined networks#2761aanand merged 2 commits intodocker:masterfrom
aanand merged 2 commits intodocker:masterfrom
Conversation
Signed-off-by: Joffrey F <joffrey@docker.com>
Containers connected to the bridge network can't have aliases, so it's simpler to rule that they can *either* be connected to the bridge network (via `network_mode: bridge`) *or* be connected to user-defined networks (via `networks` or the default network). Signed-off-by: Aanand Prasad <aanand.prasad@gmail.com>
|
LGTM! |
Closed
aanand
added a commit
that referenced
this pull request
Jan 27, 2016
Remove ability to join bridge network + user-defined networks
Author
|
Cherry-picked into #2753 |
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.
Incorporates #2757.
Containers connected to the bridge network can't have aliases, so it's simpler to rule that they can either be connected to the bridge network (via
network_mode: bridge) or be connected to user-defined networks (vianetworksor the default network).