timmattison
commented
2 years ago This is the same issue as #6190 which doesn't have any other answers
Open timmattison opened 2 years ago
timmattison
commented
2 years ago This is the same issue as #6190 which doesn't have any other answers
timmattison
commented
2 years ago The only solution I've found is to nuke everything like this:
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/dockerThen restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.
Unfortunately I still can't move my disk image storage to another drive but that's something for another day.
spencerbeggs
commented
2 years ago @timmattison Thank you. This worked for me after Docker stopped working after I upgraded to Ventura.
dhanyn10
commented
2 years ago The only solution I've found is to nuke everything like this:
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/dockerThen restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.
Unfortunately I still can't move my disk image storage to another drive but that's something for another day.
after updating several things in linux mint 21 listed in update manager, my docker stopped working, and when i've tried reinstalling even with different version, it's not working too. But, thanks to this answer my docker working again.
bazerama
commented
2 years ago The only solution I've found is to nuke everything like this:
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/dockerThen restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.
Unfortunately I still can't move my disk image storage to another drive but that's something for another day.
Had this problem on M2 Apple Silicon Mac running Monterey 12.5.1, this fixed it, not sure why it was messed in the first place :(
jsolderitsch
commented
2 years ago @timmattison suggestion worked for me. I had previously gotten a bad update experience and re-installed 4.12. This worked for awhile but I got nagged again to update to 4.13.1 and decided to try the update. It seemed to leave 4.13.1 installed but it did not run when I clicked on the Docker Desktop application icon. I saw some dormant docker processes using Activity Monitor and killed them. I trashed the updated version, freshly installed 4.13.1 using the .dmg file and it still didn't start -- same dormant docker process seen with Activity Monitor, which I killed. Then I nuked everything via the sudo command and then the freshly installed 4.13.1 did come up as expected. I am running Monterey on an Intel Mac. The update process needs some reviewing on the part of the Docker Desktop Dev team for Mac. I don't see the Fatal Error Exit Status 1 message at all. I see no errors -- docker desktop just fails to appear. Until I ran the sudo clean out command.
preston-m-price
commented
2 years ago @timmattison's suggestion unblocked me as well after I upgraded to Mac OS v 13.0/Ventura. Thanks!
shadda
commented
2 years ago I can't get it working. I restored from time machine and that completely hosed it. I've nuked every related file multiple times and it just gives me exit status 1.
MateuszBednarczyk
commented
2 years ago Same issue. I've changed the default containers path to the external device and it's crashing now.
akshaypansari
commented
2 years ago https://github.com/docker/for-mac/issues/6499 The above command didn't work. This thread solution worked for me
derekpierre
commented
2 years ago The only solution I've found is to nuke everything like this:
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/docker
This also got me back up and running (on MacOS Ventura).
ghost
commented
2 years ago Apologies to the Docker Team in advance, but the upgrade installation is not reliable. I have to uninstall everything caches etc … many times before installing a new version otherwise, I’m in for a lot of pain. This way, it usually works.
Vsion
commented
1 year ago The only solution I've found is to nuke everything like this:
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/dockerThen restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.
Unfortunately I still can't move my disk image storage to another drive but that's something for another day.
it works ! thanks
labrat1984
commented
1 year ago The only solution I've found is to nuke everything like this:
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/dockerThen restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.
Unfortunately I still can't move my disk image storage to another drive but that's something for another day.
Thank you!!! Your solution worked on Mac OS 12.6, M1 Macbook Pro (simple fast solution after much struggle!!!)
Janaka-Steph
commented
1 year ago The only solution I've found is to nuke everything like this:
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/dockerThen restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.
Unfortunately I still can't move my disk image storage to another drive but that's something for another day.
I needed to remove ~/Library/Containers/com.docker.docker also
Jdban
commented
1 year ago I needed to remove
~/Library/Containers/com.docker.dockeralso
That worked for me! This is what I ran
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/docker ~/Library/Containers/com.docker.docker
HireTheHero
commented
1 year ago In my case just restarting my Macbook works fine... I know you've tested this kind of solutions, but think twice before you nuke
codenamezjames
commented
1 year ago Here is the 2 most upvoted solutions + removal of the app it self combined (aka the nuclear option)
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/docker ~/Library/Containers/com.docker.docker /Applications/Docker.app
then i re-installed docker for apple silicone from the website
EDIT: Found this gem also. This file on mac gets super huge and apparently can cause issues also.. Its cache from what i can tell and it should be safe to delete every so often. ~/Library/Containers/com.docker.docker/Data/vms/0/data/Docker.raw
MORE EDIT: in the docker engine config on docker for desktop i modified my docker config like so and it seem to fix the issue.
{
"builder": {
"gc": {
"defaultKeepStorage": "20GB",
"enabled": true
}
},
"experimental": false,
"features": {
"buildkit": true
},
"log-opts": {
"cache-max-file": "5",
"cache-max-size": "20m",
"max-file": "5",
"max-size": "10m"
}
}
Harepitlord
commented
1 year ago @timmattison 's solution worked for me after docker-compose didn't work stating couldn't connect to the daemon after updating my mac to ventura
siddharthck
commented
1 year ago The only solution I've found is to nuke everything like this:
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/dockerThen restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.
Unfortunately I still can't move my disk image storage to another drive but that's something for another day.
Thanks!! Saved my day. I was facing same issue with following error :
beauwilliams
commented
1 year ago Works for me! Thanks 👍
4rjunc
commented
1 year ago But everytime in shutdown the system and run the docker the same error is occuers
bel-mont
commented
1 year ago The workaround works, but the error eventually comes up again and forces me to purge docker again.
prosperemebo
commented
1 year ago The only solution I've found is to nuke everything like this:
sudo rm -rf ~/Library/Caches/com.docker.docker ~/Library/Cookies/com.docker.docker.binarycookies ~/Library/Group\ Containers/group.com.docker ~/Library/Logs/Docker\ Desktop ~/Library/Preferences/com.docker.docker.plist ~/Library/Preferences/com.electron.docker-frontend.plist ~/Library/Saved\ Application\ State/com.electron.docker-frontend.savedState ~/.docker /Library/LaunchDaemons/com.docker.vmnetd.plist /Library/PrivilegedHelperTools/com.docker.vmnetd /usr/local/lib/dockerThen restart Docker and it'll fail again. Hit factory reset. Then close it. Then run this command again. And now when you restart it'll start the fresh install process.
Unfortunately I still can't move my disk image storage to another drive but that's something for another day.
Worked for me! Thanks 👍
Satbek
commented
1 year ago i just reinstalled docker-desktop and it worked for me(macos 13.5.1 , m1 chip)
doublesharp
commented
7 months ago I will get a similar error and force-quitting the com.docker.hyperkit process and then restarting Docker Desktop will let it start for me.
I can't upload diagnostics because it just hangs where it says "Diagnosing..."
Expected behavior
I should start Docker Desktop and it should let me use Docker
Actual behavior
Docker Desktop says "Fatal Error: exit status 1". It gives me the option to reset to factory defaults, diagnose, or exit. I've reset to factory defaults, uninstalled, reinstalled an older version (4.12), rebooted, and it always says the same thing.
Information
This happened when Docker ran out of space on my system. I tried to move the data directory to another drive, that hung and I had to kill Docker, now nothing works.
Output of
/Applications/Docker.app/Contents/MacOS/com.docker.diagnose checkSteps to reproduce the behavior