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

Same IP adress attribution for 2 differents containers #19086

Closed
mmicael1 opened this Issue Jan 5, 2016 · 2 comments

Comments

Projects
None yet
2 participants
@mmicael1

mmicael1 commented Jan 5, 2016

Hi all,

I have an issue with multiples containers. if i run many containers, about 150, i have two containers with same ip adress

Container 1:

"Networks": {
"bridge": {
"EndpointID": "16b37d1ca29d14b7e790a70098c700d3cd809a96d0d2ad98447243bf0cbd548e",
"Gateway": "172.17.0.1",
"IPAddress": "172.17.0.115",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:ac:11:00:73"
}
}

Container 2:

"Networks": {
"bridge": {
"EndpointID": "dec22518804cf773477f8e1c68342b6977b8b57f1cc9fbbcd33b573adadd3a7f",
"Gateway": "172.17.0.1",
"IPAddress": "172.17.0.115",
"IPPrefixLen": 16,
"IPv6Gateway": "",
"GlobalIPv6Address": "",
"GlobalIPv6PrefixLen": 0,
"MacAddress": "02:42:ac:11:00:73"
}
}

How can it be possible and how to fix it?

Thx

@thaJeztah

This comment has been minimized.

Member

thaJeztah commented Jan 5, 2016

Thanks for reporting, I think this is a duplicate of #18535, and is resolved in the latest libnetwork (#18106), which will be in Docker 1.10, see #18535 (comment)

You can already test this fix (not on a production server!) by downloading a master build from https://master.dockerproject.org

I'll close this issue, because this will be resolved in 1.10, but feel free to comment here if you're still able to reproduce this on the current master.

@thaJeztah thaJeztah closed this Jan 5, 2016

@thaJeztah thaJeztah added this to the 1.10.0 milestone Jan 5, 2016

@mmicael1

This comment has been minimized.

mmicael1 commented Jan 5, 2016

Thanks for reply

I will wait for next release and test with stop & start workaround

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