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
autogenerated LinkLocalIPv6Address can create two containers with the same ipv6 address #13211
Comments
Kudos to gissehel for his great work on investigation and the fabulous bug report! Signed-off-by: Malte Janduda <mail@janduda.net>
@gissehel thank you very much for your great work! BTW: Your code was quite good - it just has raised a type mismatch error. The Thanks! |
As explained by @mrjana in #13226 (comment), link local IPv6 generation is now left to linux (libnetwork will just construct the MAC from the IPv4) and this issue no longer exists in current docker (at least since 1.7). See o/p from latest docker:
Therefore I am suggesting to close this issue. |
Description of problem:
When I create containers without specifying any ip or mac address, ipv4, mac address and ipv6 are autogenerated (at least since version 1.5 for ipv6).
It looks like ip v4 and mac address can't conflicts, but you can generate two containers with the same ip v6:
docker version
:Client version: 1.6.1
Client API version: 1.18
Go version (client): go1.4.2
Git commit (client): 97cd073
OS/Arch (client): linux/amd64
Server version: 1.6.1
Server API version: 1.18
Go version (server): go1.4.2
Git commit (server): 97cd073
OS/Arch (server): linux/amd64
docker info
:Containers: 11
Images: 185
Storage Driver: aufs
Root Dir: /var/lib/docker/aufs
Backing Filesystem: extfs
Dirs: 207
Dirperm1 Supported: false
Execution Driver: native-0.2
Kernel Version: 3.13.0-39-generic
Operating System: Ubuntu 14.04.1 LTS
CPUs: 4
Total Memory: 15.59 GiB
Name: the server's name
ID: KU57:P757:EDQZ:P4Q2:6SF2:MLXX:WY2K:TW62:CX7C:EVHS:DORS:K6ZH
WARNING: No swap limit support
uname -a
:Linux the server's name 3.13.0-39-generic #66-Ubuntu SMP Tue Oct 28 13:30:27 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Environment details (AWS, VirtualBox, physical, etc.):
physical server
How reproducible:
Always
Steps to Reproduce:
Expected results based on how ipv6 affectation seems to work in spirit:
Actual results:
Additional info:
It seems to me that the problem lies in #8947 in the file
daemon/networkdriver/bridge/driver.go
with the line:which should look like (in spirit, I don't do go):
As I never wrote a line of go, I won't create a PR: I prefer to have someone who know what he's doing to do it.
The text was updated successfully, but these errors were encountered: