Not able to attach container to overlay network with Ipv6 enabled but works fine IP4

Continuing the discussion from Can't attach container to overlay network with Ipv6 enabled:

Hi Team,

I am also facing the same issue, anyone help here.

Can’t attach container to overlay network with Ipv6 enabled.
I’m using Docker Version 20.10.24 on Debian. I’ve been trying to attach IPv6 network while container creation time but getting below error. I was able to get it to work for the bridge driver with ip6 but when I use an overlay driver, which is what I need, it fails with below error

docker network create --driver=overlay --attachable --ipv6 --subnet 2001:db8::/64 ip6net

:~$ docker run -d --name test-export --rm --network ip6net node-export:56.1.4-2024-07-01
421de3c693b6f09003517ee3ace7d6016acbb52f9f774cb43eecf59a10f6e641
docker: Error response from daemon: attaching to network failed, make sure your network options are correct and check manager logs: context deadline exceeded.

Please share how to check overlay network related error logs or any command need to be enable for docker overlay network logs for debugging overlay network issues.

The Docker Engine CE page tells me we are currently on v27. Everyone knows IPv6 is work in progress almost everywhere, so I would update first and try again.

I was also having this issue. I got around it by using two docker networks. One network was a bridged IPv6 network so the container would have an IPv6 address. The other was an IPv4 overlay network so it could talk to containers on another host in the same swarm.

Thanks, yes for me also same behavior. bridge IPv6 and IPv4 overlay network works fine but IPv6 overly notwork only not working.

There was a big overhaul of the ipv6 implementation in docker-ce 27.0.1. So using the latest version might already include a fix for what you are looking.

It doesn’t make sense to discuss the topic with an outdated docker version, or even a non-vanilla docker version. Vanilla docker is available as docker-ce package from docker’s repositories.

I hope this is just for the sake of illustration. The prefix 2001:db8::/32 (and all subnets within the range) is reserved for documentation - that’s why you find it in documentations and blog posts, it should not be used, and is merely a placeholder that needs to be replaced with a real subnet…

1 Like

thanks for information, i will try with latest version