Error response from daemon: is vmnetd running? #6677

rbouma · 2023-01-13T09:07:01Z

I have tried with the latest version of Docker Desktop
I have tried disabling enabled experimental features
I have uploaded Diagnostics
Diagnostics ID: 1890E3D2-2574-45D2-87A9-131871CF2E43/20230113085338

Expected behavior

When running our local devstack it needs to be binding to port 53 (priviliged port) and it needs to have the vmnetd running but is isn't stated in the error:
Error response from daemon: Ports are not available: exposing port UDP 127.0.0.1:53 -> 0.0.0.0:0: failed to connect to /var/run/com.docker.vmnetd.sock: is vmnetd running?: dial unix /var/run/com.docker.vmnetd.sock: connect: no such file or directory

in the docs stated the following:
If the privileged helper process is not running, Docker Desktop prompts the user for authorization to run it under launchd.

The priviliged port helper vmnet deamon needs to be installed when a prompt pops up and give permission.

Actual behavior

The prompt for installing the deamon never pops up and throws this error:
Error response from daemon: Ports are not available: exposing port UDP 127.0.0.1:53 -> 0.0.0.0:0: failed to connect to /var/run/com.docker.vmnetd.sock: is vmnetd running?: dial unix /var/run/com.docker.vmnetd.sock: connect: no such file or directory

This happens every restart of docker for mac

Information

macOS Version: Ventura 13.1
Intel chip or Apple chip: M1 pro
Docker Desktop Version: v4.16.0

Output of `/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check`

/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0038: is the connection to Docker working?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?
No fatal errors detected.

Steps to reproduce the behavior

install docker desktop for mac 4.16.0
stop and close your docker, then start it again
docker-compose.yml >

version: "3.9"
services:
dnsmasq:
  container_name: dnsmasq
  image: rollupdev/dnsmasq
  ports:
  - mode: ingress
    host_ip: 127.0.0.1
    target: 53
    published: "53"
    protocol: udp
  restart: always

docker compose up
you got error Error response from daemon: Ports are not available: exposing port UDP 127.0.0.1:53 -> 0.0.0.0:0: failed to connect to /var/run/com.docker.vmnetd.sock: is vmnetd running?: dial unix /var/run/com.docker.vmnetd.sock: connect: no such file or directory

The text was updated successfully, but these errors were encountered:

rbouma · 2023-01-13T09:07:29Z

We fixed this temporary manually for now via:

we need to do this after every restart of docker desktop

check if the vmnetd launch service exists in /Library/PrivilegedHelperTools/com.docker.vmnetd otherwise copy them over with:

sudo cp /Applications/Docker.app/Contents/Library/LaunchServices/com.docker.vmnetd /Library/PrivilegedHelperTools/com.docker.vmnetd

check if the launch deamon exists in /Library/LaunchDaemons/com.docker.vmnetd.plist otherwise create it with:

sudo tee -a /Library/LaunchDaemons/com.docker.vmnetd.plist > /dev/null <<EOT
        <?xml version="1.0" encoding="UTF-8"?>
        <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
        <plist version="1.0">
        <dict>
                <key>Label</key>
                <string>com.docker.vmnetd</string>
                <key>Program</key>
                <string>/Library/PrivilegedHelperTools/com.docker.vmnetd</string>
                <key>ProgramArguments</key>
                <array>
                        <string>/Library/PrivilegedHelperTools/com.docker.vmnetd</string>
                </array>
                <key>RunAtLoad</key>
                <true/>
                <key>Sockets</key>
                <dict>
                        <key>Listener</key>
                        <dict>
                                <key>SockPathMode</key>
                                <integer>438</integer>
                                <key>SockPathName</key>
                                <string>/var/run/com.docker.vmnetd.sock</string>
                        </dict>
                </dict>
                <key>Version</key>
                <string>64</string>
        </dict>
        </plist>
EOT

Last step is stop the vmnetd service if it is already running, unload, load the service and then start the vmnetd service again

sudo launchctl stop com.docker.vmnetd
sudo launchctl unload /Library/LaunchDaemons/com.docker.vmnetd.plist
sudo launchctl load /Library/LaunchDaemons/com.docker.vmnetd.plist
sudo launchctl start com.docker.vmnetd

this fixed our issue. but it will be better if docker is prompting for installing the deamon to use privileged ports such as 53

aiordache · 2023-01-13T15:00:24Z

Hi @rbouma.
Looking at the logs you uploaded, we found a failed vmnetd install but no details on the actual error apart from an exit status.
You can use the commands below to remove/install vmnetd:

/Applications/Docker.app/Contents/MacOS/install remove-vmnetd
/Applications/Docker.app/Contents/MacOS/install vmnetd

Do you mind trying them and check if the install is returning an error and if you can get more details on it please? Thanks!

rbouma · 2023-01-13T19:42:56Z

@aiordache

❯ /Applications/Docker.app/Contents/MacOS/install remove-vmnetd
❯ /Applications/Docker.app/Contents/MacOS/install vmnetd
Error: parsing Info.plist: reading plist /Applications/Docker.app/Contents/Info.Plist: open /Applications/Docker.app/Contents/Info.Plist: no such file or directory

found out that the Info.plist exists

❯ ls -altrh /Applications/Docker.app/Contents/
drwxr-xr-x user admin 128 B  Thu Dec  1 11:40:33 2022  Library
drwxr-xr-x user admin  96 B  Thu Dec  1 11:40:33 2022  Frameworks
.rw-r--r-- user admin   8 B  Thu Dec  1 11:40:34 2022  PkgInfo
.rw-r--r-- user admin 7.5 KB Thu Dec  1 11:40:37 2022  embedded.provisionprofile
drwxr-xr-x user admin  96 B  Thu Dec  1 11:40:37 2022  _CodeSignature
.rw-r--r-- user admin 3.4 KB Tue Jan 10 19:20:28 2023  Info.plist
drwxr-xr-x user admin 320 B  Fri Jan 13 09:22:00 2023  .
drwxr-xr-x user admin 608 B  Fri Jan 13 09:22:03 2023  MacOS
drwxr-xr-x user admin 512 B  Fri Jan 13 09:22:05 2023  Resources
drwxr-xr-x user admin  96 B  Fri Jan 13 09:26:22 2023  ..

We are all using Case Sensitive File System so Info.Plist is non exists on the system

After rename the file with sudo mv /Applications/Docker.app/Contents/Info.plist /Applications/Docker.app/Contents/Info.Plist the install commands does work

after correcting the name docker is not starting anymore so needed it to rename it back to Info.plist

It is working now without any problem even when i restart docker desktop or the whole system the error is not seen anymore.

So i think this is an issue due to our file system that is case sensitive and the names with the Info.plist and Info.Plist

Update: 01-16-2023
Information
macOS Version: Ventura 13.1
Intel chip or Apple chip: Intel i9
Docker Desktop Version: v4.16.1

Again confirmed by a colleague running after running:

/Applications/Docker.app/Contents/MacOS/install remove-vmnetd
sudo mv /Applications/Docker.app/Contents/Info.plist /Applications/Docker.app/Contents/Info.Plist
/Applications/Docker.app/Contents/MacOS/install vmnetd
sudo mv /Applications/Docker.app/Contents/Info.Plist /Applications/Docker.app/Contents/Info.plist

it is working again.

So naming of the Info.Plist is not right.

aiordache · 2023-01-17T08:42:25Z

Sorry for this bug @rbouma. We'll get a fix in for the next release. Can you maybe duplicate the file and have it with both .Plist and .plist until then?

rbouma · 2023-01-17T09:11:54Z

@aiordache Yes i have both files in the directory and so far it is running good. Will wait for the next release thanks!

mat007 · 2023-01-20T09:42:16Z

We have just released Docker Desktop 4.16.2 with a fix!

rbouma · 2023-01-20T10:20:21Z

@mat007 great! Thanks

docker-robott · 2023-03-28T03:00:12Z

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

monaw · 2023-06-15T22:09:39Z

i know this is closed but in case this helps anyone...in my case (MacOS 13.4, Docker Desktop Version 4.20.1), the steps mentioned above by rbouma, updated on 1-16 was close but didn't work. these steps worked for me:

/Applications/Docker.app/Contents/MacOS/install remove-vmnetd
sudo /Applications/Docker.app/Contents/MacOS/install vmnetd

jonmann20 · 2023-06-22T18:45:47Z

same as @monaw was happening for me on MacOS 13.4 and Docker Desktop 4.20.1

alanzheng88 · 2023-07-16T23:27:57Z

thanks @monaw! that resolved it for me on MacOS 13.4 and docker desktop 4.20.1

kay-o · 2023-07-23T13:51:58Z

Seems several projects have begun recommending Colima when using Docker on Mac. It seems to have solved this issue; trying it out further. (Colima describes itself as "container runtimes on macOS (and Linux) with minimal setup.")

annstringer · 2023-10-05T22:45:17Z

I can confirm that the solution by @monaw worked for me on MacOS 13.5.1 and Docker Desktop 4.23.

setswei · 2023-10-19T11:11:42Z

+1 can also confirm those steps work on 13.4.1 and docker 4.24.2

marcosbrasil · 2023-10-25T13:40:23Z

+1
I can confirm that the solution by @monaw worked for me on MacOS Sonoma 14.0 and Docker Desktop 4.24.2.

mogoman · 2023-11-07T13:35:04Z

worked for me in Ventura upgrading to 4.25.0

raoulwegat · 2023-11-23T03:19:30Z

Thanks @monaw! Also working for me on Docker Desktop 4.25.2 (129061) and Sonoma 14.1.1

sebastianricaldoni · 2023-11-28T12:45:37Z

Thanks @monaw . It worked for me as well

macOS: Sonoma 14.1.1
Docker: v4.25.2 (build 129061)

dhwani07 · 2023-11-30T13:27:40Z

Thanks @monaw works for me as well macOS: 13.5.2 Ventura, Docker v 4.25

bellu · 2023-12-01T04:33:55Z

i know this is closed but in case this helps anyone...in my case (MacOS 13.4, Docker Desktop Version 4.20.1), the steps mentioned above by rbouma, updated on 1-16 was close but didn't work. these steps worked for me:

/Applications/Docker.app/Contents/MacOS/install remove-vmnetd

sudo /Applications/Docker.app/Contents/MacOS/install vmnetd

Thanks @monaw it worked on Sonoma Version 14.1 (23B74)

manoj382 · 2023-12-04T18:53:36Z

i know this is closed but in case this helps anyone...in my case (MacOS 13.4, Docker Desktop Version 4.20.1), the steps mentioned above by rbouma, updated on 1-16 was close but didn't work. these steps worked for me:

/Applications/Docker.app/Contents/MacOS/install remove-vmnetd

sudo /Applications/Docker.app/Contents/MacOS/install vmnetd

Thankful to have tracked down this thread. Worked for me!

Docker: 4.24.2 (124339 macOS: Ventura 13.6 (22G120)

slackerzz · 2023-12-14T08:03:45Z

i know this is closed but in case this helps anyone...in my case (MacOS 13.4, Docker Desktop Version 4.20.1), the steps mentioned above by rbouma, updated on 1-16 was close but didn't work. these steps worked for me:
1. /Applications/Docker.app/Contents/MacOS/install remove-vmnetd

2. sudo /Applications/Docker.app/Contents/MacOS/install vmnetd

Docker Desktop 4.26.0 on MacOS Sonoma 14.2

This helped, but after that, I constantly needed to run docker system prune, otherwise, each time I start my containers (via docker compose) I get something like this:

Error response from daemon: network 0903dc942d8d6f31628875418f6e873f3872b61fd69c45e108eecd43d162e8ba not found

mitrol-design · 2024-01-10T11:02:23Z

One more for @monaw ’s solution - macOS Sonoma 14.2.1 & Docker Desktop 4.26.1 — Thanks

RootProgger · 2024-01-15T12:43:57Z

Same Problem on MacOS X Ventura, Docker Desktop 4.26.1.
@monaw solution works, but I can't every time go to the Sysadmin when i restart Docker-Desktop to call Sudo

StephenHinck · 2024-01-22T16:50:20Z

MacOS Sonoma 14.2.1 with Docker Desktop v4.26.1, same issue and same fix from @monaw worked great. Would be great to get this fixed directly and not require a workaround.

nucsemin · 2024-02-01T08:06:04Z

Thanks a lot @rbouma. This solution worked for me.

taoeffect · 2024-05-09T16:50:22Z

I am running v4.29.0 on Sonoma 14.4.1, and still had to run @monaw's commands to get this to work.

Sounds like this hasn't been fixed? Can the issue be reopened?

StephenHinck · 2024-06-13T20:55:36Z

Updated to v4.31.0 today and it re-broke me. #6677 (comment) is still necessary to resolve this issue :-/

RootProgger · 2024-06-14T12:50:29Z

Updated to v4.31.0 today and it re-broke me. #6677 (comment) is still necessary to resolve this issue :-/

i resolved this issue on my Mac with complete deinstall docker desktop (including remove config files) and reinstall new version.

ThePlastic · 2024-06-15T08:51:52Z

Updated to v4.31.0 today and it re-broke me. #6677 (comment) is still necessary to resolve this issue :-/

i resolved this issue on my Mac with complete deinstall docker desktop (including remove config files) and reinstall new version.

tried, issue still present

marcosbrasil · 2024-06-17T14:00:33Z

I can confirm the same here as @StephenHinck

StephenHinck · 2024-06-17T15:12:12Z

@ThePlastic - reinstall has worked for me so far (and the fix has persisted through one upgrade). Follow the full instructions here: https://docs.docker.com/desktop/uninstall/, including the three terminal commands.

KurtRogers · 2024-07-04T10:03:07Z

Insane. @monaw you are a legend. The commands are still needed.

Docker v4.31.0 (153195)

MacOS 14.5 (23F79)

ThePlastic · 2024-07-04T10:10:46Z

@ThePlastic - reinstall has worked for me so far (and the fix has persisted through one upgrade). Follow the full instructions here: https://docs.docker.com/desktop/uninstall/, including the three terminal commands.

I didi it, step by step, still need the 2 commands listed above....

brittonwalker · 2024-07-22T18:41:27Z

The solve that worked for me was going to Settings -> Advanced and selecting "Allow privileged port mapping".
If it is already selected, which in my case was, I had to uncheck, apply changes, and check again. Solved my issue.

ryan-ashbrook · 2024-08-05T06:16:30Z

i know this is closed but in case this helps anyone...in my case (MacOS 13.4, Docker Desktop Version 4.20.1), the steps mentioned above by rbouma, updated on 1-16 was close but didn't work. these steps worked for me:

/Applications/Docker.app/Contents/MacOS/install remove-vmnetd

sudo /Applications/Docker.app/Contents/MacOS/install vmnetd

Worked for me as well.

carbone · 2024-08-13T17:25:10Z

i know this is closed but in case this helps anyone...in my case (MacOS 13.4, Docker Desktop Version 4.20.1), the steps mentioned above by rbouma, updated on 1-16 was close but didn't work. these steps worked for me:

/Applications/Docker.app/Contents/MacOS/install remove-vmnetd

sudo /Applications/Docker.app/Contents/MacOS/install vmnetd

Worked for me as well.

Same. Thanks!

kevinquillen · 2024-08-22T21:03:54Z

This still happens (reported to me several times this week) and yet the issue is closed, and the fix is still to run the two commands.

working-name · 2024-09-20T15:51:38Z

@mat007 maybe a regression but it's not fixed in 4.20.1

timohuisman · 2024-10-17T13:48:18Z

i know this is closed but in case this helps anyone...in my case (MacOS 13.4, Docker Desktop Version 4.20.1), the steps mentioned above by rbouma, updated on 1-16 was close but didn't work. these steps worked for me:

/Applications/Docker.app/Contents/MacOS/install remove-vmnetd

sudo /Applications/Docker.app/Contents/MacOS/install vmnetd

Still got the issue in 4.34.3, ^ fixes the problem for me aswel.

RalucaElisabetaR · 2024-12-04T08:32:15Z

We fixed this temporary manually for now via:

we need to do this after every restart of docker desktop

Had same issue after updating to Docker to 4.36.0 and this fixed it ✔️✔️

skoskie · 2025-01-23T18:59:48Z

4.37.2 Checking in. Still an issue. Still resolved by...

/Applications/Docker.app/Contents/MacOS/install remove-vmnetd
sudo /Applications/Docker.app/Contents/MacOS/install vmnetd

working-name · 2025-01-23T19:04:29Z

Yup, still an issue. I gave up hope, so I placed the commands in a function in $HOME/.zshrc to make it easier to run every time:

function fixdocker() {
  sudo /Applications/Docker.app/Contents/MacOS/install remove-vmnetd
  sudo /Applications/Docker.app/Contents/MacOS/install vmnetd
}

All you do is type fixdocker like you do docker compose .... Function name = command, so it can be anything you want.

rbouma · 2025-01-23T19:09:18Z

Original issue creator here: After all the issues I had in the past with Docker Desktop, I finally switched to a new Docker replacement called OrbStack. Check it out if you’re looking for something with fewer problems and much faster performance, including shorter startup times: https://orbstack.dev/

skoskie · 2025-01-30T16:24:18Z

I've heard of Orb and been wanting to try it out, but I need to research how disruptive the switch would be and I've just been way too busy to even think about it lately. I'm pretty dependent on DDev and not sure if they are compatible. Definitely glad to hear another positive comment about it though. Docker is so unreliable.

crstauf · 2025-01-30T16:35:54Z

I need to research how disruptive the switch would be

@skoskie For me, there was no disruption. Picked it up immediately.

dependent on DDev and not sure if they are compatible

One of my projects uses DDev and works fine with OrbStack.

rbouma · 2025-01-30T16:39:26Z

@skoskie yes for me also, used mix of DDEV, Warden, RollDev and its al good and working correctly. OrbStack is also giving you a migration option to seamlessly transfer all projects, containers, volumes and images so you will not loose any data :)

docker-robott added the version/4.16.0 label Jan 13, 2023

mat007 closed this as completed Jan 20, 2023

brianyoungblood mentioned this issue Jan 24, 2023

Docker desktop 4.15.0 cannot connect to docker.vmnetd with macOS Monterey version 12.6 #6611

Open

1 task

docker-robott added the lifecycle/locked label Mar 28, 2023

anilnatha mentioned this issue Nov 9, 2023

Test ability to run SMD codebase locally NASA-PDS/portal-wp#80

Open

GrantBirki mentioned this issue Jan 9, 2024

Issues with port 389 GrantBirki/ldap-api#8

Closed

ntilagoa mentioned this issue Jan 23, 2024

MacOS port 53 conflict with mdnsresponder qdm12/dns#136

Open

nucsemin mentioned this issue Feb 1, 2024

Docker requires a processor with virtualization capabilities and hypervisor support. #7156

Closed

reynoldsalec mentioned this issue May 13, 2024

Issue with new MacOS installation script lando/setup-lando#40

Closed

jenlampton mentioned this issue Jul 26, 2024

Docker won't work on M1 macOS 14.5 (23F79) #7300

Open

Error response from daemon: is vmnetd running? #6677

Error response from daemon: is vmnetd running? #6677

Comments

rbouma commented Jan 13, 2023 • edited Loading

Expected behavior

Actual behavior

Information

Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check

Steps to reproduce the behavior

rbouma commented Jan 13, 2023 • edited Loading

aiordache commented Jan 13, 2023

rbouma commented Jan 13, 2023 • edited Loading

aiordache commented Jan 17, 2023

rbouma commented Jan 17, 2023 • edited Loading

mat007 commented Jan 20, 2023

rbouma commented Jan 20, 2023

docker-robott commented Mar 28, 2023

monaw commented Jun 15, 2023

jonmann20 commented Jun 22, 2023

alanzheng88 commented Jul 16, 2023

kay-o commented Jul 23, 2023 • edited Loading

annstringer commented Oct 5, 2023

setswei commented Oct 19, 2023

marcosbrasil commented Oct 25, 2023

mogoman commented Nov 7, 2023 • edited Loading

raoulwegat commented Nov 23, 2023

sebastianricaldoni commented Nov 28, 2023

dhwani07 commented Nov 30, 2023

bellu commented Dec 1, 2023

manoj382 commented Dec 4, 2023

slackerzz commented Dec 14, 2023

mitrol-design commented Jan 10, 2024

RootProgger commented Jan 15, 2024 • edited Loading

StephenHinck commented Jan 22, 2024

nucsemin commented Feb 1, 2024

taoeffect commented May 9, 2024

StephenHinck commented Jun 13, 2024

RootProgger commented Jun 14, 2024

ThePlastic commented Jun 15, 2024

marcosbrasil commented Jun 17, 2024

StephenHinck commented Jun 17, 2024

KurtRogers commented Jul 4, 2024

ThePlastic commented Jul 4, 2024 • edited Loading

brittonwalker commented Jul 22, 2024

ryan-ashbrook commented Aug 5, 2024

carbone commented Aug 13, 2024

kevinquillen commented Aug 22, 2024 • edited Loading

working-name commented Sep 20, 2024

timohuisman commented Oct 17, 2024

RalucaElisabetaR commented Dec 4, 2024 • edited Loading

skoskie commented Jan 23, 2025

working-name commented Jan 23, 2025

rbouma commented Jan 23, 2025 • edited Loading

skoskie commented Jan 30, 2025

crstauf commented Jan 30, 2025

rbouma commented Jan 30, 2025

rbouma commented Jan 13, 2023 •

edited

Loading

Output of `/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check`

rbouma commented Jan 13, 2023 •

edited

Loading

rbouma commented Jan 13, 2023 •

edited

Loading

rbouma commented Jan 17, 2023 •

edited

Loading

kay-o commented Jul 23, 2023 •

edited

Loading

mogoman commented Nov 7, 2023 •

edited

Loading

RootProgger commented Jan 15, 2024 •

edited

Loading

ThePlastic commented Jul 4, 2024 •

edited

Loading

kevinquillen commented Aug 22, 2024 •

edited

Loading

RalucaElisabetaR commented Dec 4, 2024 •

edited

Loading

rbouma commented Jan 23, 2025 •

edited

Loading