for-mac
for-mac copied to clipboard
docker
Docker desktop 4.15.0 cannot connect to docker.vmnetd with macOS Monterey version 12.6
- [x ] I have tried with the latest version of Docker Desktop
- [x ] I have tried disabling enabled experimental features
- [x] I have uploaded Diagnostics
- Diagnostics ID: 199C8593-A7C2-4D16-BF59-1C09DDAB632E/20221202073517
Expected behavior
~ docker pull hello-world
Using default tag: latest
latest: Pulling from library/hello-world
2db29710123e: Pull complete
Digest: sha256:faa03e786c97f07ef34423fccceeec2398ec8a5759259f94d99078f264e9d7af
Status: Downloaded newer image for hello-world:latest
docker.io/library/hello-world:latest
Actual behavior
Error response from daemon: Get "https://registry-1.docker.io/v2/": read tcp 192.168.65.4:61388->192.168.65.5:3128: read: connection reset by peer
Information
- macOS Version: macOS Monterey version 12.6
- Intel chip or Apple chip: intel
- Docker Desktop Version: 4.15.0
Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check
[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] 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?
[PASS] DD0012: is the VM networking working?
[SKIP] DD0030: is the image access management authorized?
[FAIL] DD0019: is the com.docker.vmnetd process responding? failed to ping vmnetd with error: 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
[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?
1 failures detected
1 : is the com.docker.vmnetd process responding?
Failed with: failed to ping vmnetd with error: 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 com.docker.vmnetd process is needed to create symlinks for CLIs in your path.
self-diagnose took 12.100303387s
Steps to reproduce the behavior
- Clean install of docker desktop 4.15.0 (either via .dmg to applications or by following command line steps)
- docker login && || docker pull hello-world
I have resolved this issue by running a clean install of docker desktop v4.14.1
Had the same issue as @425devon but with intel running Ventura 13.1. I had to remove 4.15.0 and install 14.14.1. Reinstalling 4.15.0 didn't help me. Same solution as @425devon.
I upgrade from 4.10 to 4.15 and get the same errors, the fix was to downgrade to 4.14.1 👍 my specs: OS: Monterey - macOS 12.6 (21G115) Processor: 2.6 GHz 6-Core Intel Core i7 Ram: 32GB
Version 14.6.2 seemed to solve the problem for me, and I believe it was based on this issue as well. https://github.com/docker/for-mac/issues/6677
Ran into a similar issue with Docker Desktop 4.16+ but with a different error message:
% docker pull alpine:3.7
Error response from daemon: Get "https://registry-1.docker.io/v2/": unexpected EOF
Spent quite a bit of time trying out numerous different solutions before coming to the same conclusion as the rest of you: Docker Desktop 4.14.1 works, 4.15.0 does not.
I was in contact with a Docker support person trying to debug the issue (I initially did not realise it was due to a Docker Desktop update) and they were unable to refer to this thread either.
MacBook Pro 2019 (Intel), MacOS Ventura 13.1
There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.
Prevent issues from auto-closing with a /lifecycle frozen comment.
/lifecycle stale
@425devon did you figure this out? Do you have the download link for Docker v4.14.1? It's not on the release notes page.
