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 Swarm networks not working over IPv6 #33398

meyskens opened this Issue May 25, 2017 · 1 comment


None yet
3 participants

meyskens commented May 25, 2017


When setting up Docker Swarm over IPv6 everything works fine except setting up an overlay network. The network can be used when on the same server but when trying to reach a container on another server it doesn't work, they are also not listed in the peers under docker network inspect. The journald logs keep telling Docker isn't able to add itself to a memberlist.

May 25 14:11:18 swarm-node-ldn1 dockerd[459]: time="2017-05-25T14:11:18.935435123Z" level=error msg="Failed to join memberlist [2a01:7e01::f03c:91ff:fe60:5b29] on retry: 1 error(s) occurred:\n\n* Failed to resolve 2a01:7e01::f03c:91ff:fe60:5b29: too many colons in address 2a01:7e01::f03c:91ff:fe60:5b29"

It seems to indicate that it is unable to recognize that this is an IPv6.

Steps to reproduce the issue:

  1. Set up Docker Swarm on at least 2 servers over IPv6
  2. Create an overlay network
  3. Try to make a service access another service on another server

Describe the results you received:
Networks not able to connect to another server. With the above logs.

Describe the results you expected:
Ability to connect to other services.

Output of docker version:

 Version:      17.05.0-ce
 API version:  1.29
 Go version:   go1.7.5
 Git commit:   89658be
 Built:        Thu May  4 22:04:27 2017
 OS/Arch:      linux/amd64

 Version:      17.05.0-ce
 API version:  1.29 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   89658be
 Built:        Thu May  4 22:04:27 2017
 OS/Arch:      linux/amd64
 Experimental: false

Additional environment details (AWS, VirtualBox, physical, etc.):
Running on Linode with the Debian kernel for VXLan support


This comment has been minimized.

webologics commented Jan 3, 2018

@meyskens How was this resolved? I see the behavior you are describing still in 17.09.

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