for-mac
for-mac copied to clipboard
docker
Docker for mac doesn't work on IPv6 network
Expected behavior
Docker for mac works on IPv6 network.
Actual behavior
Docker for mac doesn't work on IPv6 network.
Information
Documentation states: "IPv6 is not yet supported on Docker for Mac":
- https://docs.docker.com/docker-for-mac/troubleshoot/#workarounds-for-common-problems
#704 links to some issues and there are many others mentioning IPv6, but all of them are closed like broken IPv6 is a normal state of affairs. This issue can be closed when either:
- IPv6 works out of the box.
- Documentations states that IPv6 will never be supported.
Steps to reproduce the behavior
- Install docker for mac on a machine with dual-stack network.
- Run a container,
ping6 google.comin it. - Despair.
Thanks for your request for IPv6 support -- I've escalated it to the networking team.
@djs55 Is there any progress in supporting ipv6? It's an actual blocker for us :(
There's been a little progress -- I recently fixed a bug in the IPv6 support within the Mirage TCP/IP stack which is used inside Docker for Mac. I think the next task is to configure the router discovery in vpnkit
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.
Prevent issues from auto-closing with an /lifecycle frozen comment.
If this issue is safe to close now please do so.
Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale
According to Google, IPv6 global usage has reached 25% (source: https://www.google.com/intl/en/ipv6/statistics.html?25%#tab=ipv6-adoption). Maybe the "network team" could look into this again? Let's embrace the future!
Cant believe apps still ignore ipv6 in 2020... ipv6 is not the future, its actually now.
You can enable ipv6 on Docker on Linux...
Why not mac?
According to Google, IPv6 global usage has reached 25%
That was 2 years ago. It's now little over 31%. But some countries are close to, or passed 50%.
@PhilETaylor It's worse than that, there are some things that are much better approached assuming an IPv6 network and how they are designed with later developments backfilling IPv4 (or not).
I had an IoT project that we had to start with IPv4 due to too low penetration of IPv6. The engineering cost was 30% higher, and I doubt that the design bugs that arose from assuming IPv4 have yet been ironed out.
This issue has been open for 3+ years now and makes Docker desktop on Mac unusable for some people. Are there any serious plans to actually implement this ?
It's very sad that IPv6 still ignored by Docker team. It brings many troubles for my tasks and make Docker unusable as development environment at our internal networks that IPv6 only
In spite of the message to the contrary on these docs, following these instructions with Docker for Mac appears to work.
In spite of the message to the contrary on these docs, following these instructions with Docker for Mac appears to work.
I added {"ipv6": true, "fixed-cidr-v6": "2001:db8:1::/64"} as well (and rebooted later).
But it doesn't work on my desktop.
$ docker run -it alpine ash
/ # ifconfig -a
eth0 Link encap:Ethernet HWaddr 02:42:AC:11:00:02
inet addr:172.17.0.2 Bcast:172.17.255.255 Mask:255.255.0.0
inet6 addr: 2001:db8:1::242:ac11:2/64 Scope:Global
inet6 addr: fe80::42:acff:fe11:2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1156 (1.1 KiB) TX bytes:516 (516.0 B)
/ # ip -6 route
2001:db8:1::/64 dev eth0 metric 256
fe80::/64 dev eth0 metric 256
default via 2001:db8:1::1 dev eth0 metric 1024
ff00::/8 dev eth0 metric 256
/ # ping6 2001:db8:1::1
PING 2001:db8:1::1 (2001:db8:1::1): 56 data bytes
64 bytes from 2001:db8:1::1: seq=0 ttl=64 time=0.421 ms
64 bytes from 2001:db8:1::1: seq=1 ttl=64 time=0.302 ms
^C
/ # ping6 ipv6.tsinghua.edu.cn
PING ipv6.tsinghua.edu.cn (2402:f000:1:881::8:205): 56 data bytes
# it hangs here
May I ask what your macOS version is? And the Docker Desktop version? Thanks.
In spite of the message to the contrary on these docs, following these instructions with Docker for Mac appears to work.
The "following these instructions" link goes to a page titled "Enable IPv6 Support", which includes a note: "Note: IPv6 networking is only supported on Docker daemons running on Linux hosts."
Unlike IPv4, IPv6 address prefixes are not normally statically defined, so modifying a config file like this is suboptimal/incomplete.
Is it possible to make donation or something else to change issue priority? This bug is very annoying...
In spite of the message to the contrary on these docs, following these instructions with Docker for Mac appears to work.
No, it won't work. I just tried. Docker for mac runs in a very special type of separate network which prevents ipv6 from working at all.
I ended up running docker inside multipass instead, and it works with ipv6 network out of the box, why not Docker Desktop! Other free solutions like VirtualBox also works while not the non-free Docker Desktop solution.
I ended up running docker inside multipass instead, and it works with ipv6 network out of the box, why not Docker Desktop! Other free solutions like VirtualBox also works while not the non-free Docker Desktop solution.
Docker is simply deprecated technology. It is advisable to migrate to another containerization solution.
This was opened back in 2017. Any updates? I would accept we are still working on this. Just some sort of communication would be grateful. I really need this feature.
