Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed a few network UI issues in swarm-mode #24158

Merged
merged 1 commit into from
Jul 5, 2016
Merged

Conversation

mavenugo
Copy link
Contributor

* Detect name conflicts on network creation
* Detect and prevent network connect/disconnect for managed containers

Signed-off-by: Madhu Venugopal <madhu@docker.com>
@thaJeztah
Copy link
Member

Are we sure we want to introduce a concept of "managed" and "unmanaged" containers?

How does this resolve creating a local network named "test", if there's an overlay network with the same name?

@mavenugo
Copy link
Contributor Author

@thaJeztah we have a few cases where we have to differentiate managed and unmanaged containers (mostly due to the current limitations that we have with a few unsupported features). When we are feature parity, then we can relax these restrictions and maybe remove this differentiation as well.

How does this resolve creating a local network named "test", if there's an overlay network with the same name?

That's exactly this PR does with the changes in api/server/router/network/network_routes.go.

@tonistiigi
Copy link
Member

LGTM

@vdemeester
Copy link
Member

LGTM 🐸

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

docker network create -d bridge test works if there is already an overlay network named test?
7 participants