Reputation: 929
I have installed Docker Desktop version 4.4.4 and it is not running. It only displays "Docker Desktop Starting ..." but never starts running.
I have tried so many ways but didn't solve:
Upvotes: 73
Views: 115883
Reputation: 1191
To resolve this issue follow the below steps.
Just delete the temporary files from the following.
C:\Windows\Temp
C:\Users\{yourAccountName}\AppData\Local\Temp
C:\Windows\Prefetch
then
Upvotes: 7
Reputation: 1147
The main problem is WSL2 does not auto install the kernel when WSL2 installs, yet Docker Desktop expects it already installed. So, fully close & stop Docker as other answers have said, then run this cmd as admin:
wsl --update
Now open Docker Desktop & it should start up ok.
edit: This answer should be unnecessary now, as Docker Desktop v4.22 shows this on first run, if it had to install WSL2 as part of its installation.
I noticed it still hung again the next time, after I chose Quit & ran the update & Restart Docker. I had to then Quit Docker yet again, open yet again the app, & wait about 1 or 2 minutes for it to finish its initial startup ok. It may be faster on newer PCs, as mine for now is Win10 22H2 with only 4gb ram. I will test again on Win11 22H2 on newer PC, in few weeks.
Upvotes: 112
Reputation: 83
wsl --unregister docker-desktop
wsl --unregister docker-desktop-data
This worked for me.
Found on https://debugah.com/solved-docker-forever-in-docker-is-starting-at-windows-task-714/
Upvotes: 1
Reputation: 29
On Windows 10 Pro (10.0.19045.3208)
After doing the following:
1.wsl --install from command prompt
2.Docker Desktop v4.22.0 installation
Starting Docker Desktop got stuck with message "Starting the Docker Engine"
Shutting down the machine and starting again fixed it.
Upvotes: 0
Reputation: 4098
This worked for me.
wsl --install -d Ubuntu
And no loss with pulled images. It's all retained.
Upvotes: 0
Reputation: 14419
My fresh install was experiencing the same symptoms. Also wsl --list
showed "no installed distributions". I tried many reinstallations and restarts of Docker and WSL, but eventually found the steps:
Got it working on on Windows 11 Enterprise.
Upvotes: 1
Reputation: 3606
As wrote here, you need to do:
wsl --update
But after that it doesn't fix my issue until I did restart to my pc.
Upvotes: 2
Reputation: 1
I am running windows 11, visual studio 2023 and had this issue.
First, open a command prompt and type
wsl.exe --list --online
Then enter following
wsl.exe --install Ubuntu-20.04
Then type in the prompt sudo apt update
to update the distribution. Lastly, start up Docker desktop and log in (you can register at their site). That fixed Docker on my pc.
Upvotes: 0
Reputation: 53
wsl -v
if it show version then linx is install search windows programer feature in your laptop enable virtulization
wsl --set-default-version 2
restart laptop and then start docker and wait for 2 minutes your docker will start working
Upvotes: 0
Reputation: 41
got to services and stop Docker desktop service and start again
reopen Docker desktop it will work
Upvotes: 1
Reputation: 1
In my case it helped me to enable the CPU SVM (Support Vector Machine) function in my BIOS settings.
Also, if you have this feature disabled, you will not be able to use Virtual Box either.
Upvotes: 0
Reputation: 11
for me it worked in windows (docker desktop):
Upvotes: 1
Reputation: 11
I was also having the same problem, just a few minutes ago.
Platform: Windows 10 Pro - 22H2 - Build 19045.2486
Windows Updates newly installed: KB5022282, KB5020876, KB5012170
What i did was: Activating the Windows Hypervisor Platform
And it did solve the problem, atleast for now
Upvotes: 0
Reputation: 1089
I use Docker with PyCharm. I ran into this problem when I launched PyCharm and Docker Desktop at about the same time.
On my machine Docker Desktop starts automatically when I boot. I can avoid the problem by waiting for Docker Desktop to finish starting. And then start PyCharm.
Upvotes: 0
Reputation: 51
Solved this issue with @Alvi answer Docker forever in "Docker is starting.." at Windows task
I guess you are using wsl2 features. In that case, open PowerShell or command prompt and type: optionalfeatures.exe
scroll down and uncheck
Windows Subsystem for Linux
apply the changes and restart your computer.
After restart follow the previous steps again and check
Windows Subsystem for Linux
and restart again. Hopefully now your docker will run
Upvotes: 5
Reputation: 61
For me, it was a problem with WSL. When I tried:
wsl --install -d Ubuntu
in a command window, after a few minutes I got error 0x80370114
The fix was to do:
Then reinstall/restart Docker Desktop, and it works!
Hope this helps someone else
Upvotes: 6
Reputation: 2175
I was facing same code for for Docker version 4.*. For me it was Visual Studio code,
Stopped WSL form Task manager
stopped Docker which was showing "Docker desktop is starting" form Task manage
stopped Visual Studio code form Task manager
Started Docker again
These steps placed my Docker in Running state in 30 seconds
Hope this helps someone!
Upvotes: 5
Reputation: 382
What worked for me was to log in into the Docker (upper right corner), but when I first clicked on login, it said "exec: "rundll32": executable file not found in %PATH%" - I search and found that I need to check environmental variable in PATH that I have "C:\WINDOWS\system32" there - (and in my case I really had it broken somehow - don't know why, but I missed backslash between Windows and system32). So I fixed to correct path, restarted PC. Then I was able to login. And immediately "Docker Desktop Starting..." was gone.
Upvotes: 0
Reputation: 30643
I've found out another symptom leading to the solution is also related to WSL.
On one side, Docker service won't start throwing this error:
error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version": open //./pipe/docker_engine: The system cannot find the file specified.
And on the other, WSL is unresponsive. Attempting to run a WSL Distro or WSL command directly on CMD, won't return any output at all. It will just hang in there.
So the solution is common to WSL and Docker. I've found in a question regarding the WSL issue, that the LxssManager Windows service is staled (it may show under services.msc as Stopping and all the buttons are greyed out, or I've even seen it Running apparently, but with the Docker and WSL issues above, so something is wrong with it still.)
First, we have to get LxssManager PID in order to kill it. Using an elevated shell, we can get it this way:
sc queryex LxssManager
Having the PID, we can kill the process but beware I wasn't able to kill it using kill
or taskkill
commands. I was getting the following error:
ERROR: The process with PID XXXXX could not be terminated.
Reason: Access is denied.
To effectively kill the process, do as following:
wmic process where ProcessID=XXXXX delete
Replace XXXXX with PID, of course. Having done so, start the LxssManager service:
net start LxssManager
A word of warning: I've noted in some cases this is not enough for unknown (to me) technical reasons even if LxssManager service is shown as Running. Just repeat the above steps! Sometimes it works doing this once, sometimes doing it twice for some reason.
TL;DR
Upvotes: 24