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

Docker network connect cli has problem connecting a container with portmapping #17824

Closed
coolljt0725 opened this issue Nov 9, 2015 · 2 comments
Assignees
Labels
priority/P1 Important: P1 issues are a top priority and a must-have for the next release.
Milestone

Comments

@coolljt0725
Copy link
Contributor

When a container has port mappings, it will failed to connect to other network.
Step to reproduce:

$ docker run -d --name test1  -p 5000:5000 busybox top
a2119164c5bee543d7c3cc4e128826290d114c18095dbf268b2014835b625f6b
$ docker network connect test test1
Error response from daemon: failed to create endpoint test1 on network test: Bind for 0.0.0.0:5000 failed: port is already allocated
$

docker version
Client:
Version: 1.10.0-dev
API version: 1.22
Go version: go1.4.2
Git commit: e357be4
Built: Mon Nov 9 12:25:37 UTC 2015
OS/Arch: linux/amd64

Server:
Version: 1.10.0-dev
API version: 1.22
Go version: go1.4.2
Git commit: e357be4
Built: Mon Nov 9 12:25:37 UTC 2015
OS/Arch: linux/amd64

@GordonTheTurtle
Copy link

Hi!

Please read this important information about creating issues.

If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.

If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.

This is an automated, informational response.

Thank you.

For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues


BUG REPORT INFORMATION

Use the commands below to provide key information from your environment:

docker version:
docker info:
uname -a:

Provide additional environment details (AWS, VirtualBox, physical, etc.):

List the steps to reproduce the issue:
1.
2.
3.

Describe the results you received:

Describe the results you expected:

Provide additional info you think is important:

----------END REPORT ---------

#ENEEDMOREINFO

@mavenugo
Copy link
Contributor

mavenugo commented Nov 9, 2015

ping @sanimej

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/P1 Important: P1 issues are a top priority and a must-have for the next release.
Projects
None yet
Development

No branches or pull requests

3 participants