macvlan driver doesn't work in MacOS

[ajoldham]

Continuation of : https://github.com/docker/for-mac/issues/3447 as it was auto-closed. This isn't fixed in the latest Docker Edge 19.03.2 with MacOS 10.14.6.

---

$ ifconfig en9 en9: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=4 ether 58:ef:68:7d:06:05 inet6 fe80::1028:71b1:5694:b4bf%en9 prefixlen 64 secured scopeid 0x12 inet 10.42.34.91 netmask 0xfffffc00 broadcast 10.42.35.255 nd6 options=201<PERFORMNUD,DAD> media: autoselect (1000baseT ) status: active $ docker network create -d macvlan --subnet=10.42.32.0/22 --gateway=10.42.32.1 -o parent=en9 pub_net Error response from daemon: invalid subinterface vlan name en9, example formatting is eth0.10

[maxpavlov]

+1

If you specify eth0 in parent, it will get created, but won't work =)

[ViperRNMC]

same problem here with en0

[adocehic]

I've been losing my mind in various attempts in getting macvlan working, and this is why. Blindly using eth0 instead of the actual en0 interface appears to work when it shouldn't.

[obmuc]

Any workarounds for this?

[HunterDG]

following

[amaisano]

Still not working in Docker 2.2.0.4.

[adocehic]

I ended up buying a Dell R620. It was easier to actually set up a whole linux server to really take advantage of Docker than it was to waste time working around this bug or waiting for it to get fixed.

It's rather annoying as this is a very clear and reproducible bug that on the surface appears to be simple.

On Jan 7, 2020, at 2:19 PM, obmuc notifications@github.com wrote:

Any workarounds for this?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/docker/for-mac/issues/3926?email_source=notifications&email_token=ABUXDOJHGHKJO523LWEJ7NLQ4T5VPA5CNFSM4I2V6M62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEIKPQFA#issuecomment-571799572, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABUXDOKNKYUF7D7JAQ6RSP3Q4T5VPANCNFSM4I2V6M6Q.

[amaisano]

@adocehic are you saying typing eth0 actually works with en0 (even though it shouldn't)?

[mastix]

I can confirm that it's still not working with Docker Desktop 2.2.0.5 & Docker 19.03.8.

[rfoltz]

@mikeparker I think we would really wish for this to be implemented for Mac OS, this is stopping me from using Docker in my home lab.

[dciancu]

Still not working with Docker Desktop 2.3.0.4 & macOS 10.15.6

[dinhkk]

docker network create -d macvlan \
  --subnet=192.168.2.0/24 \
  --gateway=192.168.2.1 \
  -o parent=eth0 \
  my-macvlan-net

I have tested above command on my macOSX 10.15.6. This seems to be a lie. It works. But ifconfig does not show eth0, but en0

[ajoldham]

Thanks. It seems to configure, but when I run a container using that network, I can't seem to ping or communicate out of it.

[ctyrider]

Yes, macOS Docker allows configuring macvlan bound to parent eth0 interface (which doesn't exist on the host). Multiple Containers placed in that macvlan can communicate with each out, but not out of the host.. which is what I would expect when binding a network to a phony adapter.

Any thoughts on when we can actually see this fixed? Disappointing that core Docker feature like this doesn't work on macOS.

[Alexivia]

This would be such a useful feature... I can confirm that on my Mac I can't configure a macvlan network interface with Docker version 19.03.13, build 4484c46d9d.

[michaelprescott]

It's looking like this bug might not be getting fixed for a while. What are other options? How else can we configure and launch a set of containers via 'docker-compose up' to make them accessible to other machines on a LAN?

[michaelprescott]

And, same failure for ipvlan. I wish Docker docs made this bold and clear that both are broken on macOS. I learned a lot trying to solve it, but ultimately it was a waste of time for me.

It takes a little longer to setup what I need with VMs and VMWare Fusion, but it works. Interestingly, in Fusion it's categorized under the "Bridged Networking" configuration. Noting that, I circled back to Docker and tried setting up a bridged network. Still no luck. The containers still don't appear on the LAN. Anyhow, if you are free to move to a linux development machine where macvlan and ipvlan work, here are some really great articles about macvlan https://hicu.be/tag/macvlan

[mminks]

Confirmed.

[onlinefchen]

Confirmed.

waiting

[docker-robott]

Issues go stale after 90 days of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30 days 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

[barinet]

/lifecycle frozen

[barinet]

/remove-lifecycle stale

[Rubberduck1971]

/remove-lifecycle stale

[Rubberduck1971]

/lifecycle frozen

[fdevans]

+1

[pkishino]

+1

[thueske]

+1

[arrrgi]

+1

[joaoceron]

+1

[Edisonliiii]

+1

[Abirdcfly]

+1

[owalid]

+1

[junoteam]

+1

[jamauai]

+1

[bournex]

+1

[jkneer]

+1

[pablosed]

+1

[francisgro]

+1

[pgasiorowski-es]

+1

[mjanson]

+1

[michaelprescott]

+1

[conotto]

+1

[rcmarini]

+1

[dineshkumar-vi]

+1

[oshadhavg]

Issue is till in Docker version 20.10.11, build dea9396

[oshadhavg]

Issue is till in Docker version 20.10.11, build dea9396

Not working in Docker version 20.10.12, build e91ed57 as well.

[oshadhavg]

Is there a workaround for this? This docker macvlan is not working on either MACOS or Windows. This is really a frustrating situation. Please resolve this!

[rcmarini]

You can try creating a reverse proxy on the host machine, redirecting a local port to the remote service you need to call, and calling the host port through the container. Resolves for some types of services.

[phonezhou]

s there a workaround for this? This docker macvlan is not working on either MACOS or Windows. This is really a frustrating situation. Please resolve this!

[wojciechowskidawid]

+1