for-mac icon indicating copy to clipboard operation
for-mac copied to clipboard

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

Open tbogdan opened this issue 1 year ago • 4 comments

Description

Docker won't work on M1 macOS 14.5 (23F79). Screenshot 2024-05-29 at 16 57 25 Screenshot 2024-05-29 at 16 58 04 Screenshot 2024-05-29 at 17 02 45 Screenshot 2024-05-29 at 17 02 52

Reproduce

Install Docker Run it.

Expected behavior

to work

docker version

docker version
Cannot connect to the Docker daemon at unix:///Users/bogdan/.docker/run/docker.sock. Is the docker daemon running?
Client:
 Cloud integration: v1.0.35+desktop.13
 Version:           26.1.1
 API version:       1.45
 Go version:        go1.21.9
 Git commit:        4cf5afa
 Built:             Tue Apr 30 11:44:56 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

docker info

Client:
 Version:    26.1.1
 Context:    desktop-linux
 Debug Mode: false

Server:
ERROR: Cannot connect to the Docker daemon at unix:///Users/bogdan/.docker/run/docker.sock. Is the docker daemon running?
errors pretty printing info

Diagnostics ID

84DBDFFD-833D-4FE1-9869-7B45796D4E83/20240529135503

Additional Info

macOS 14.5 (23F79), Memory: 32GB, CPU: Apple M1 Max, Latest Docker 4.30.0 I think it is related to Apple VM; it just won't work, and I couldn't find a solution. Any help is appreciated! TY!

tbogdan avatar May 29 '24 14:05 tbogdan

According to the diagnostic, the installation did not completed fully: the config.json file for example is missing some entries.

Can you uninstall Docker (following this documentation), then reinstall it?

jpbriend avatar May 30 '24 14:05 jpbriend

According to the diagnostic, the installation did not completed fully: the config.json file for example is missing some entries.

Can you uninstall Docker (following this documentation), then reinstall it?

Hi, thanks for your reply! I done uninstall/reinstall tens of times, before posting here, even I used a big list of possible remains to remove, got from different discussions. I've did it again according with the docs you mention, nothing changed, it still isn't working.

PS: I mention that I have two M1 MBP, one from work (M1 Max), the other is personal one (M1 Pro), (os is the same/latest) the issue is manifesting identically on bouth.

tbogdan avatar May 31 '24 05:05 tbogdan

I'm also seeing this same issue on my Mac M1 Pro running Sonoma 14.5 (23F79).

Resetting to factory defaults did not change the behavior.

Can you uninstall Docker (following this documentation), then reinstall it?

This link (which assumes you can start Docker) is of no help to me since I can't even get Docker to start. It states:

From the Docker menu, select the Troubleshoot icon in the top-right corner of Docker Dashboard and then select Uninstall.

How do you get to the "Docker menu" if Docker refuses to start? Or more importantly, how do you uninstall Docker if it refuses to start?

I'm running the diagnostics now, but it says "Diagnosing..." and has for the past 5 minutes, which makes me think it may have crashed again.

jenlampton avatar Jul 26 '24 21:07 jenlampton

I was eventually able to uninstall Docker via command line, and reinstall. After reinstalling docker still would not run from the command line, stating

"docker": executable file not found in $PATH 

I manually added docker to $PATH (I think this is supposed to happen automatically on install, but it did not) and then docker would start, but it would not run any containers, stating:

Ports are not available: exposing port TCP 127.0.0.1:443 -> 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 fix from https://github.com/docker/for-mac/issues/6677#issuecomment-1593787335 ended up resolving that issue for me, and now Docker will both start and run my containers :)

jenlampton avatar Jul 26 '24 22:07 jenlampton