search

docker / for-mac

Bug reports for Docker Desktop for Mac
https://www.docker.com/products/docker#/mac
2.43k stars 118 forks source link

Docker for mac doesn't work on IPv6 network #1432

Open bobrik opened 7 years ago

bobrik commented 7 years ago

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":

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:

Steps to reproduce the behavior

  1. Install docker for mac on a machine with dual-stack network.
  2. Run a container, ping6 google.com in it.
  3. Despair.
djs55 commented 7 years ago

Thanks for your request for IPv6 support -- I've escalated it to the networking team.

dfilatov commented 7 years ago

@djs55 Is there any progress in supporting ipv6? It's an actual blocker for us :(

djs55 commented 7 years ago

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

aaranmcguire commented 6 years ago

Are you able to provide any update to this issue?

docker-robott commented 6 years ago

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

aaranmcguire commented 6 years ago

/remove-lifecycle stale

nikolaymatrosov commented 6 years ago

Are there any updates?

docker-robott commented 5 years ago

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

boutetnico commented 5 years ago

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!

aaranmcguire commented 5 years ago

/remove-lifecycle stale

aaranmcguire commented 5 years ago

/lifecycle frozen

alvassin commented 5 years ago

Is still a big problem. Are there any news/plans on this issue?

PhilETaylor commented 4 years ago

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?

mdavids commented 4 years ago

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%.

timcoote commented 4 years ago

@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.

bkda commented 4 years ago

" IPv6 is not the future, its actually now."

SRv6d commented 4 years ago

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 ?

onevelik commented 3 years ago

Any news please?

andre487 commented 3 years ago

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

mtharrison commented 3 years ago

In spite of the message to the contrary on these docs, following these instructions with Docker for Mac appears to work. Screenshot 2021-02-10 at 19 58 39 Screenshot 2021-02-10 at 19 59 19

coppercash commented 3 years ago

In spite of the message to the contrary on these docs, following these instructions with Docker for Mac appears to work. Screenshot 2021-02-10 at 19 58 39 Screenshot 2021-02-10 at 19 59 19

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.

timcoote commented 3 years ago

In spite of the message to the contrary on these docs, following these instructions with Docker for Mac appears to work. Screenshot 2021-02-10 at 19 58 39 Screenshot 2021-02-10 at 19 59 19

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.

tarmolov commented 3 years ago

Is it possible to make donation or something else to change issue priority? This bug is very annoying...

andrewchen5678 commented 2 years ago

In spite of the message to the contrary on these docs, following these instructions with Docker for Mac appears to work. Screenshot 2021-02-10 at 19 58 39 Screenshot 2021-02-10 at 19 59 19

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.

andrewchen5678 commented 2 years ago

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.

uplsh580 commented 2 years ago

My OS is macOS 12.1. I'm still having a same problem.

SRv6d commented 2 years ago

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.

mdavids commented 2 years ago

Any news?

SiirRandall commented 2 years ago

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.

peredwardsson commented 2 years ago

Also curious. Major functionality for me lost here.

sklevenz commented 1 year ago

Ping6!

chyroc commented 1 year ago

Hello, is there any update, the support for ipv6 is really necessary, thanks

SiirRandall commented 1 year ago

I agree needing to have IPv6 for macOS is a needed for me here.

xsoheilalizadeh commented 1 year ago

It would be great if we have some comments from team members, what are the challenges to have IPv6 support? Is there any blocking?

cellulosa commented 1 year ago

Any updates?

akimrx commented 1 year ago

up, when?

SRv6d commented 1 year ago

For anyone looking for a more modern docker desktop experience with IPv6 support, OrbStack has worked great for me.

spence commented 1 year ago

For anyone looking for a more modern docker desktop experience with IPv6 support, OrbStack has worked great for me.

+1000 to this. Faster. Can't tell a difference.

Enable ipv6 in settings:

image
VectorZhao commented 11 months ago

Any updates?

PhilETaylor commented 11 months ago

I think everyone here has moved to Orbstack.dev which provides (amongst other things) ipv6 out of the box - built by a single person, with impressive features and releases, performance and speed improvements.

I literally dont know a single developer still using Docker Desktop for Mac.

Even if Docker Desktop for Mac added ipv6 support today, I know I'll not be returning to use it. Unsubscribing this thread now also.

maxpain commented 7 months ago

any updates?

mohit-zangoh commented 5 months ago

Still no updates? 🙂

bobrik commented 5 months ago

Please do not post "any updates?", it's not helping.

No0ne commented 2 weeks ago

Solved it by adding this at the beginning of docker-compose.yml:

networks:
  default:
    enable_ipv6: true
djs55 commented 2 weeks ago

We've been adding IPv6 support over the last several releases of Docker Desktop. The next release will have even better support. If you'd like to try a development build:

The new Settings / Resources / Network screen has new options:

Screenshot 2024-09-26 at 10 29 27

Dual stack v4/v6 is default, but you can switch to v4-only (if you have problems with partially-working v6 in your environment) or v6-only (it's the future)

Note by default (to avoid breaking changes to containers) in dual stack v4/v6 environments, docker networks don't have v6 addresses. To fix that, do what @No0ne has suggested above in compose, or use docker network create --ipv6. See the IPv6 documentation