Docker for Mac hangs while starting up. Stuck on "Docker Desktop is Starting"

[rje0929]

• I have tried with the latest version of my channel (Stable or Edge)
• I have uploaded Diagnostics
• Diagnostics ID: 9516E931-4567-4F91-AACB-30019CED0937/20201209185508

Expected behavior

Docker starts up

Actual behavior

Docker doesn't start and just hangs with the "Docker Desktop is Starting" message.

Information

• macOS Version: 10.15.7

Diagnostic logs

Docker for Mac: 10.15.7

Steps to reproduce the behavior

1. Just double click the Docker app to start. It also does it on restarting.

[keepitreal]

I ran into this same issue. Resetting to factory defaults resolved it for me. From the docker menu click Troubleshoot -> Reset to factory defaults. Then you can go back in and reconfigure it to how you'd customized it.

[gabor-boros]

Same here. Factory reset helps, but that's the last thing what I wanted to do.

[tudoramariei]

The same thing has been happening to me but starting with version 3.0.0 and also after the update to 3.0.1
I tried every red button (uninstall, reset to factory, clean/purge) and nothing seems to have worked 😓

Mac Version: 10.15.7 | Diagnostics ID: B842B454-F385-4603-8534-A8ABFAB4A4B2/20201214070142

[glitterlip]

I ran into this same issue. Resetting to factory defaults resolved it for me. From the docker menu click Troubleshoot -> Reset to factory defaults. Then you can go back in and reconfigure it to how you'd customized it.

Then you have to recreate all your containers.

[kiziltas]

Happened to me too after this workaround attempt. 3.0.1, 3.0.0, 2.5.0.1 and 2.5.0.0 all have the same issue. Only downgrading to 2.4.0.0 worked for me.

[tudoramariei]

Seems like it wasn't a Docker issue on my side, but rather the antivirus was blocking/throttling Docker

[colceagus]

@tudoramariei

Seems like it wasn't a Docker issue on my side, but rather the antivirus was blocking/throttling Docker

Same for me. but the corporate firewall and antivirus (McAfee) resets once every x minutes. It also throttles my internet speed and pushes to the internal docker registry.

What did you do/add to the antivirus to fix it?

I was not able to add /var/lib/docker to the scanning exceptions. I've added the containers from Library to the scanning exceptions as per the official documentation . I've added the whole docker app to the firewall allow list for both inbound and outbound, for any IP, any Port.

[tudoramariei]

@colceagus well, it also McAfee on my side and I don't have the slightest clue on what needs changing
Talk to your local friendly SysAdmins (since they're the ones who made the changes for me); I don't have access to the configs, just to their results ‾_(ツ)_/‾

What (I think) I can tell is that the Firewall seems to affect the network connection and not the files themselves. I also had a drop in internet speed to a 0.5MB/s from about 10MB/s at a point

[tiborvass]

Hi folks, can someone upload a newer diagnostics ID ? I can't find the two mentioned on this issue Looks like I couldn't get the docker daemon logs from them, but the diagnostics were successfully uploaded. I have a suspicion on what causes this, but would need to confirm from the daemon logs.

[tiborvass]

@rje0929 I could be wrong but I believe you are hitting #5131 on which I provided a workaround, please let me know if that helped or if you still see your issue.

[kodywilson]

@tudoramariei Thanks for mentioning the McAfee firewall! I was facing the same issues, Docker Desktop would stay in starting forever, and what fixed it for me was opening up the McAfee firewall for the Docker application. I had tried the factory reset, but it didn't help at all. Once I monkeyed with the firewall settings it started working right away...

[gpongelli]

I've found a workaround to get docker 3.2.0 working on Mac Catalina 10.15.7 since the first docker startup.

1. after downloaded the docker dmg file and copied the Docker.app to Application, do NOT run the Docker.app from Application folder.
2. Run Docker.app from the mounted dmg window, it'll work
3. go to preferences -> Resources -> file sharing and REMOVE the folders like /private and /Library . Keep only /Users, /Volumes and /tmp
4. close running Docker app
5. now open the Docker.app from Application folder

For me, this workaround solves the issue.

[fsutawanir]

I've found a workaround to get docker 3.2.0 working on Mac Catalina 10.15.7 since the first docker startup.

1. after downloaded the docker dmg file and copied the Docker.app to Application, do NOT run the Docker.app from Application folder.
2. Run Docker.app from the mounted dmg window, it'll work
3. go to preferences -> Resources -> file sharing and REMOVE the folders like /private and /Library . Keep only /Users, /Volumes and /tmp
4. close running Docker app
5. now open the Docker.app from Application folder

For me, this workaround solves the issue.

I'm doing this in Mojave 10.4.6.

• Do step no. 2, event though I only have Docker.dmg v2.5.0.1
• Do step no.3
• Then install using homebrew to install Docker Desktop v3.2.2

It's working, thank you very much.

[aayushrangwala]

Re-installing worked for me
https://stackoverflow.com/questions/44346109/how-to-easily-install-and-uninstall-docker-on-macos

[kahitarich]

I another user on my computer and while logged in as that use Docker started just fine. That gave me the clue. Removing the .docker folder in my home and restarting is the only step that worked for me.

[shannon-slattery]

How long is the reset to factory defaults supposed to take? mine has been running for 20+ minutes now and no new pop-ups have.... popped up.

[LumberSzquatch]

I'm not sure if what I experienced was exactly what was happening here, but for anyone else stumbling upon this thread via Google search, like I did, the issue for me was that Docker Desktop was never prompting me to accept their new terms of service.

It took me restarting Docker itself a couple of times and even restarting my machine for it to pop up, though even then it wasn't popping up. When it did eventually show up and after accepting it, it started successfully and showed me all my containers. I have no idea what I did to make it finally show itself, but when it did, it started working as expected.

So I guess double check that somehow before you commit to factor resetting or reinstalling and potentially losing your containers.

[KlausVii]

I'm not sure if what I experienced was exactly what was happening here, but for anyone else stumbling upon this thread via Google search, like I did, the issue for me was that Docker Desktop was never prompting me to accept their new terms of service.

It took me restarting Docker itself a couple of times and even restarting my machine for it to pop up, though even then it wasn't popping up. When it did eventually show up and after accepting it, it started successfully and showed me all my containers. I have no idea what I did to make it finally show itself, but when it did, it started working as expected.

So I guess double check that somehow before you commit to factor resetting or reinstalling and potentially losing your containers.

This was the issue for me this morning, how silly an issue.

[slifty]

Just came to say that this whole situation is MIND BLOWINGLY UNACCEPTABLE.

Between the ridiculous new TOS and the broken functionality, I'm so disappointed in docker for mac and the way it treats its users.

[Hermanverschooten]

My issue is that I cannot have docker auto-starting on log in. When I reboot my iMac, i get a popup, that I cannot close, telling me docker failed to start. Eventually CleanMyMac tells me there is a non-responding app 'docker', if I then close it, and restart it, it works fine. Happens every reboot.

Docker desktop: 4.1.1 (69879)
MacOS BigSur 11.6

[0x000bff]

This is the second time in the past month or so I've had Docker break while updating and need to reinstall.
In both instances:

• Docker icon says there's an update
• I download and install update
• Accept new ToS
• Docker hangs on "Starting..."
• I eventually quit Docker Desktop and restart
• Docker unusable, rapidly flips between "Starting" and "Stopping"

Docker Desktop 4.1.1
MacOS 11.4

I don't remember what version Docker Desktop was for the first incident.

[Bojne]

I also had this issue due to low memory in my machine. Clean extra files then docker is all-set.

[atakemura]

I had this issue after an update, but it resolved itself by: Quit Docker Desktop, Manually Kill com.docker.hyperkit (Force Quit), then restarting Docker Desktop.
MacOS 11.6, Docker Desktop 4.2.0.

[acatxnamedvirtue]

Docker started rapidly flipping between Starting and Stopping after updating to Docker Desktop (Mac) 4.2.0 (70708).
The steps listed above by @atakemura fixed it for me. Thank you @atakemura !!

[anatawa12]

With 4.3.0 (71786), This happens. . On the console,VM failed with Internal Virtualization error. The virtual machine failed to start. error by com.docker.virtualization exists but it looks like it's ignored.

[orenpinei]

Rebooting may MAC solved the issue

[nomadme]

Docker hangs on "Starting..." "Stopping..."
after updating resources on the docker desktop.

OS: Mac Monterey, 12.1, M1 Pro chip
Docker Desktop 4.3.2 (72729)

No solution works until RESET TO FACTORY.

[demeralde]

@public-rant I have a kill switch enabled for my VPN too, although it seemed to be working with Docker most of the time. So I'm not sure what's going on there.

[xiaolinone]

I deleted ~/Library/containers/com.docker.docker/backend.lock. It seems to be working for me.

[florestankorp]

I deleted ~/Library/containers/com.docker.docker/backend.lock. It seems to be working for me.

On top of that I had to disable the "Kill switch" of my VPN client. Looks like it's working now...fingers crossed!

[florestankorp]

Nope. False alarm. It's still hanging, crashing and definitely not solved...had to uninstall and reinstall AGAIN for the 100th time...no clue what's going on

Docker Desktop 4.13
MacBook Air M1

[myugen]

Same issue here, gets stuck everytime. Uninstalled and reinstalled.

[aprilmintacpineda]

I'm experiencing this when I startup my pc, docker is configured to run on startup but for some reason it takes forever and seems to be stuck on starting.

[endangurura]

Same issue here, stuck on starting. Uninstalled and reinstalled, no success.
MacBook Pro M1

[smark91]

4.14 not working too
MacBook Pro M1 Max

Revert to 4.12 works

[jstm88]

Just encountered the issue on 4.13.1 - Docker suddenly stopped working and refused to restart.

I honestly can't believe this is the "quality" that Docker deems acceptable. As of now I'm eliminating Docker from my toolchain. It's not worth the trouble.

[mauroservienti]

I'm using 4.14.1 on macOS Ventura (13.0.1) and facing this issue. "Reset Docker to factory defaults" doesn't work as a workaround. The only thing that works for a while is rebooting, which is unacceptable.

Is there a way to download previous version bits? On the Docker website the only option seems to be to download only the latest.

[yattias]

Click the docker icon => Troubleshoot => Reset to defaults & clear cache

[jstm88]

Click the docker icon => Troubleshoot => Reset to defaults & clear cache

This is only a band-aid since the same problem will recur. Plus, any "solution" that deletes data or settings is a massive red flag. Why would I ever trust anything important to Docker considering that?

Frankly, Docker needs to mark their Mac software as "pre-alpha" to establish more reasonable expectations. Claiming that they "support" the Mac is false advertising.

[PaleNeutron]

Nothing but restart OS worked for me.

[ArtemChekunov]

I was trying to apply the new default-address-pools but Docker Desktop start crashing at the start and the Reset Docker to factory defaults didn't help.

So I did:

1. echo '{}' > ~/.docker/daemon.json
2. start the Docker Desktop
3. rm all containers and networks

docker rm $(docker ps -qa)
docker network rm $(docker network ls -q)

4. apply my new config with default-address-pools

[henrik242]

So I finally managed to solve this by uninstalling Docker Desktop and switch to colima instead.

$ brew install docker docker-compose colima
$ colima start --memory 8 --cpu 4

Voila, docker and docker-compose works just as before, without the annoyance of Docker Desktop!

[dschiavu]

I'm having this issue when clicking on Restart on the Docker icon's context menu - check the screenshot - Docker freezing and all the menu options getting disabled. Rebooting the system usually resolves it. Thought this one might be related to this issue.

[oluwaseye]

I tried few solutions given in the comments above but found no luck. The solution given here worked for me: https://stackoverflow.com/a/44346110/5118708
Details:

Operating System: MacOs Big Sur 11.6 (intel)

Step 1: Quit docker Step 2: Clean everything including images, containers etc. using: (plz take backup if necessary)

sudo rm -f /usr/local/bin/docker
sudo rm -f /usr/local/bin/docker-machine
sudo rm -f /usr/local/bin/docker-compose
sudo rm -f /usr/local/bin/docker-credential-osxkeychain
sudo rm -Rf ~/.docker
sudo rm -Rf $HOME/Library/Containers/com.docker.docker  # here we delete stored images, If you dont want to delete SKIP THIS STEP

Step 3: Install docker via command line using brew install:

brew install --cask docker  (correct command, the one given on SO didn't work for me.)

Step 4: Open Docker. After this my docker was up and running!
Hope this helps! 🤞

Had the same issue here on macOS 12.1 Intel Chip and this worked for me !

Thanks been stuck for a while on this issue 😓 👍

You are a rock star!!! thanks. This worked for me

[bobwurtz]

@oluwaseye Your reply was very helpful - thank you! I'm using Monterey 12.6 with the Apple chip and I had to add a few steps to what you described.

sudo rm -f /usr/local/bin/docker
sudo rm -f /usr/local/bin/docker-machine
sudo rm -f /usr/local/bin/docker-compose
sudo rm -f /usr/local/bin/docker-credential-osxkeychain
sudo rm -Rf ~/.docker
sudo rm -Rf $HOME/Library/Containers/com.docker.docker  # here we delete stored images, If you dont want to delete SKIP THIS STEP

# I added the steps below, clearing all docker references from /usr/local/bin
sudo rm -f /usr/local/bin/com.docker.cli
sudo rm -f /usr/local/bin/docker-credential-ecr-login
sudo rm -f /usr/local/bin/docker-index               
sudo rm -f /usr/local/bin/kubectl.docker
sudo rm -f /usr/local/bin/vpnkit

Then I downloaded Docker from the website and it started working.

[deendin]

I had this same issue on a Mac M1, I was so patient to follow this steps:

1. I restarted my machine
2. Started docker and the error still remains the same
3. I signed in to docker, and went back to quit my docker
4. I started it again and docker is back.

[bgok]

I also tried re-installing Docker. During the re-installation, I noticed a release note that says docker won't work when virtual box is installed. After Virtual Box was uninstalled, the project started fine.

[hscheib]

I have been stuck on an old Docker Desktop version (4.8.1) for the past year because every new version hangs when starting for me on my M1 macbook. I noticed I hadn't updated my macOS in a while. I updated to latest macOS 13.4.1 and then updated to latest Docker Desktop 4.21.1 and Docker Desktop started successfully! So my solution seemed to be getting to a latest macOS version

[Steellow]

For me it started working after I downloaded Docker from their official website. Installing with homebrew caused it to stuck

[srosato]

For me, it started working after I purged everything manually... I used ncdu to find where Docker had let a mark (60 GB of containers + VM within my user directory) and purged all and re-installed.

Since my setup is easy to reproduce I did not mind to start fresh again.

[nashaad]

This worked for M1, Ventura
(Docker Desktop installation from official site)

1. Delete/Uninstall Docker Desktop from Applications

2. Cleanup. These steps are from another discussion

rm -rf Library/Group\ Containers/group.com.docker
rm -rf Library/Containers/com.docker.docker
rm -rf Library/Application\ Support/Docker\ Desktop

3. Install from official website again

[huelsgp27]

same issue, reset works but it will happen again

[balusarakesh]

wow!!! 4 years old issue still happening on a paid platform
for me the fix is to completely restart my mac

[CharanMN7]

User on M2, Sonoma 14.5 here.
This happened with me too. Restart was able to fix it. Not sure if it's gonna come back but, I guess another restart will do the job.