No Docker daemon on MacOS intel #7553
Comments
|
@nbdavies I was having the exact same issue as you but I just managed to fix it. Here are the exact steps, as best as I am able to remember them. Before solution: I had attempted multiple uninstalls/reinstalls, and including attempting to uninstall things manually, and eventually completing a fresh install via brew. Steps in my solution: After entering these commands a single line at a time, I was able to resolve my issue with docker. My previous version of docker had been installed ~October 12, 2024, and I just saw the Mac malware notice pop up yesterday (January 20, 2025). That's when this issue began, and I attempted to do a clean install of docker and ran into this error. Initially, I had try copy/pasting all the commands into a terminal window at once, and I got an error or something (don't recall exact thing). Here is the error I got when I tried pasting the whole script into my Mac terminal: I think I also tried putting it into shell file (.sh), ensuring it was executable with chmod, and then running it, but I don't remember what happened. Just to be clear, this is basically exactly the situation I found myself in: Hope this helps! |
|
@michaelcosley I appreciate the spirit in which the suggestion was given. Sounds like you were running into #7527, and the remediation steps from #7527 worked for you. That's great. Sounds like you are not one of the users affected by this issue. To be able to say I did, I ran through those steps for the nth time too ✔ , and I'm still experiencing the issue described above. |
|
I'm not sure if my issue is the same as yours, but my Docker Desktop app was also not initializing the daemon, and the application window was never being initialized either. I was using the same version as you (4.37.2), on the most recent version of MacOS (15.2), but running on an M1 Max chip. My issue was resolved by uninstalling Docker Desktop through AppCleaner, restarting my computer, then reinstalling. Maybe that helps. I noticed that many symbolic links were not being deleted when I just deleted the ".app" file from the Applications/ directory, and AppCleaner found many more related files which remained on my system. |
Description
Docker commands persistently fail with a message
ERROR: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?This is occurring after going through all remediation steps in #7527 (including restarting Docker Desktop, restarting the machine, uninstalling/reinstalling version 4.37.2
Troubleshoot > Get Support output
(Docker Desktop is in fact running.)
Upon starting Docker Desktop, there's this error notification:
Attempting to update settings in Docker Desktop flashes this error message:
(That includes making any changes to Settings > Extensions to resolve the previous error.)
Docker Desktop does not quit when this option is selected (it requires Force Quit instead):
This collection of symptoms leads me to suspect that a rushed patch for the "malware" bug may have created other bugs, particularly for MacOS intel users. (Teammates with MacOS Apple Silicon (M1, M2...) are not seeing this issue.)
Reproduce
docker infoCannot connect to the Docker daemon at (path). Is the docker daemon running?Expected behavior
Docker daemon should be running
docker version
$ docker version Client: Version: 27.4.0 API version: 1.47 Go version: go1.22.10 Git commit: bde2b89 Built: Sat Dec 7 10:35:43 2024 OS/Arch: darwin/amd64 Context: default Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?docker info
Diagnostics ID
Diagnose Failed
Additional Info
Daemon logs from
~/Library/Containers/com.docker.docker/Data/log/vm/containerd.log:The text was updated successfully, but these errors were encountered: