Installed docker desktop for windows, after having installed the linux kernel update package and changing to wsl 2 version (virtualization is enabled) but i get the message «Docker Desktop stopped…» as shown below.
Tried:
- uninstalling and reinstalling again
- run application as administrator
asked Feb 11, 2022 at 18:13
Yanis Yanis
5971 gold badge4 silver badges8 bronze badges
7
I had the same problem. If you are using docker 4.5.0, try uninstall and install 4.4.4 instead. That worked for me.
answered Feb 11, 2022 at 20:48
3
A new version of Docker Desktop (4.5.1), released on 2022-02-15 fixes this problem.
If you are running Docker Desktop on Windows Home, installing 4.5.1 will switch it back to WSL 2 automatically. If you are running another version of Windows, and you want Docker Desktop to use the WSL 2 backend, you must manually switch by enabling the Use the WSL 2 based engine option in the Settings > General section. Alternatively, you can edit the Docker Desktop settings file located at %APPDATA%Dockersettings.json and manually switch the value of the wslEngineEnabled field to true.
answered Feb 15, 2022 at 16:32
2
I also get the same problem after updating my Docker version from 4.4.4 to 4.5. It was crashed when I want to run my container today. I try to reinstall with 4.5 version and get the error «Docker Desktop stopped…». Then, I try to reinstall with 4.4.4 version, and now it just run perfectly fine like before.
answered Feb 13, 2022 at 15:09
1
Also had this issue on Mac (Intel chip) after updating to v4.5.0.
Reinstalling and a system restart solved the issue.
answered Feb 28, 2022 at 1:20
1
- I have tried with the latest version of Docker Desktop
- I have tried disabling enabled experimental features
- I have uploaded Diagnostics
- Diagnostics ID: Diagnostic is not available too
Actual behavior
Docker Desktop freeze at Docker Desktop stopping
.
Expected behavior
- At install stage Docker asks which mode I preffers
- Docker settings available at any time. On changing smth it will restart containers
- Docker app starts and allows to switch used mode
Information
Several months I didn’t use Docker at Windows 10 Pro(v.4.2). Today I’ve tried to start it. It freezes at «Docker Desktop starting» stage.
I’ve tried to remove and install Docker Desktop. As I understand it tries to start at WSL2 (Why you can’t ask it at install stage?)
How can I switch it to Hyper-V mode if it can’t start?
Why setting are not available while full app with all containers will be loaded?
Same here with Docker Desktop 4.5.1 running on an Win 10 Pro Azure VM. On startup it says that WSL is missing, but then is stuck in Docker Desktop stopping
state, which means that it is not possible to switch to Hyper-V backend.
Hi @Eugentis, If you want to switch to Hyper-V you can edit the $env:APPDATADockersettings.json
file and set wslEngineEnabled
to false
.
We’re looking how we can improve the settings and unblock them for such tasks.
Thanks @StefanScherer
But disabling app settings is not the best solution in real world. It should be available independent on Docker engine status
Same here with Docker Desktop 4.5.1 running on an Win 10 Pro Azure VM. On startup it says that WSL is missing, but then is stuck in
Docker Desktop stopping
state, which means that it is not possible to switch to Hyper-V backend.
Also having this issue, with same version of Docker on Win 10.
A solution that worked for me from the front-end: Go to docker desktop —> Troubleshoot —> Clean / Purge data —> click on wsl 2 and delete.
Once removed, the docker deamon restarted and it worked fine.
madhurasri, kunalshahare28, thutuephan, sbswarna, akankshaAzilen, oscarmandley, Alimo3, rhamybachourinfra, debWhittle263, ikshita-madhub-cko, and 8 more reacted with heart emoji
upandreluiz, otecdima, and andrewkirc reacted with rocket emoji
@ajay16bharadwaj it works if your dashboard is active
But Docker has some strange behaviour with it.If you started or stoped container all dashboard wil be disabled
As for me it is very strange approach
Facing same issue ..Any fix for this?
A solution that worked for me from the front-end: Go to docker desktop —> Troubleshoot —> Clean / Purge data —> click on wsl 2 and delete.
Once removed, the docker deamon restarted and it worked fine.
This worked for me, thanks!
I have tried every thing still i am unable to open the docker it is stuck on docker desktop stopped…… Any help?
Try to update the WSL (.msi extension). after installing this app is working fine.
I have tried latest Docker 4.9.0
, the key is
I tried all the stuff already posted above but all to no avail. I realized that each time I restarted the docker desktop app, a «WSL 2 Installation incomplete» pop-up message comes. I clicked the link and reinstalled the kernel update and it worked.
Faced the same problem. Restarted my pc and it started working.
Eu tentei o Docker mais recente
4.9.0
, a chave é
Após executar esse comando e reiniciar a máquina, o docker desktop funcionou corretamente!
After running this command and restarting the machine, docker desktop worked correctly
Make sure after Docker For Desktop (Windows) installation thatWSL (Windows subsystem for Linux) is installed.
before your linux configuration machine, at powershell: wsl —set-default-version 2
It is solved my issue.
Hi @Eugentis, If you want to switch to Hyper-V you can edit the
$env:APPDATADockersettings.json
file and setwslEngineEnabled
tofalse
.We’re looking how we can improve the settings and unblock them for such tasks.
This worked for me, Thanks.
I am able to run Docker Desktop by following below steps.
-
Use WSL V2 to smoothly run Docker Desktop. To set default wsl version to v2, run
wsl.exe --set-default-version 2
-
Install your Linux flavor. I tried with Ubuntu-18.04 by running command:
wsl --install -d Ubuntu-18.04
-
Above command will install ubuntu with WSL V2, but to make sure you can run command:
wsl.exe --set-version Ubuntu-18.04 2
-
To check the version of your installed linux flavor and respective wsl version:
wsl.exe -l -v
-
Then freshly install Docker Desktop for Windows. It should start running within sometime.
Hi, I also ran into this problem, I don’t know exactly what happened, But I think it should be wsl that went wrong, because my wsl can’t be opened; After I referred to this answer, I did a reset of the network.
I executed the following two commands:
netsh int ip reset
netsh winsock reset
And restarted my computer,I can open my wsl now:
I have tried latest Docker
4.9.0
, the key is
This work for me as well …
(update: after few restart I am still facing the problem)
temporary solution (which work for me)
Powershell
- Force stop docker desktop (task manager)
- Run
wsl --shutdown
in power shell - Start docker desktop again
I ran into this problem today.
This is really bad, I wish they can fix it soon.
Hardware: ASUS TUF DASH F15
Software: Windows 10 Home 21H2 (OS build: 19044.1826)
Docker Version: latest as of today ( I was not able to go to the settings page. It was running forever)
Here were the list of things I tried but didn’t work:
- Uninstalled the current version and installed the latest on docker official website.
- Go to Troubleshoot on docker desktop and click «Clean/Purge data» (click on wsl 2 and delete)
- Go to Troubleshoot on docker desktop and click «Reset to factory defaults»
- Edit the $env:APPDATADockersettings.json file and set wslEngineEnabled to false
At least point I found that my WSL was broken by trying to get Docker to work.
I was not able to try the solutions provided above that relates to running the wsl command.
Whenever I typed wsl, it was waiting forever on my terminal and nothing happened.
The fact that Docker destroyed my WSL really pissed me off because I relied on WSL to do all the source
control on my machine and interact with remote machines.
I tried all the stuff already posted above but all to no avail. I realized that each time I restarted the docker desktop app, a «WSL 2 Installation incomplete» pop-up message comes. I clicked the link and reinstalled the kernel update and it worked.
This issue will be resolved by modifying the settings.json file.
1- Path of the file: C:Users<username>AppDataRoamingDockersettings.json
2- Set «wslEngineEnabled»: false
Hi @Eugentis, If you want to switch to Hyper-V you can edit the
$env:APPDATADockersettings.json
file and setwslEngineEnabled
tofalse
.We’re looking how we can improve the settings and unblock them for such tasks.
Already did and still not working.
Try following.
- If there is a VPN running, try disconnecting VPN and restart Docker Desktop.
- Click on troubleshoot (bug) icon on the right top corner, perform a factory reset, and purge data.
To resolve this issue, as shown in dialog “Docker Desktop – Install WSL2 kernel update” we need to download from the reference link mentioned in dialog – https://aka.ms/wsl2kernel
Install the WSL2 kernel update then restart Docker. This should work
Image for reference
Either Docker or Windows should do something for this. None of the solution is working for me.
A solution that worked for me from the front-end: Go to docker desktop —> Troubleshoot —> Clean / Purge data —> click on wsl 2 and delete.
Once removed, the docker deamon restarted and it worked fine.This worked for me, thanks!
This worked for me.
Thank you, you saved my hours! 👍
I am experiencing the same issue and trying to resolve that issue as at the moment.
Deleting the data sets does not appear to work. Docker has been stuck in «Shutting Down», and cannot be quit. It has been showing this for over an hour:
Same issue here on Windows 11. It was working fine the whole day, and it suddenly crashed.
I tried the following:
- Reset networking (netsh int ip reset + netsh winsock reset)
- Updated WSL (wsl —update)
- Purge Data
- Upgraded to latest version
Before the upgrade, the application was stuck on «Stopping Docker».
After the upgrade, the application is stuck on «Docker Desktop Starting»
C:Usersusername>wsl.exe -l -v
NAME STATE VERSION
* Ubuntu Running 2
Workaround:
- Completely uninstall Docker Desktop on Windows 11
- Opened a terminal with Linux subsystem (WSL), and installed Docker with the CLI (article) as I’m not using any Windows images.
Damn so many people out there are facing this issue.
I don’t know what is @docker or Windows(for WSL) doing about this.
I thought only Windows users are facing this but looks like we’ve got Mac as well.
Solution:
So I have almost tried all the above workarounds but what worked for me is I installed little older version of docker and then both WSL as well as Docker started working fine.
Hope it helps to everyone.
A solution that worked for me from the front-end: Go to docker desktop —> Troubleshoot —> Clean / Purge data —> click on wsl 2 and delete.
Once removed, the docker deamon restarted and it worked fine.This worked for me, thanks!
how long does it usually take to delete?
The solution is simple if you are on Windows 10/11 using «Dockers Desktop for Windows»
When Dockers Desktop for Windows installs it looks like it does not bother to check the OS being used and defaults to «Linux Containers». This fails on Windows 10 or 11 and causes the «Docker Is Starting» freeze. (I also saw numerous uncaught Promise errors in the docker logs related to this, too).
To fix this, simply go to your Notifications/System Tray area of Windows in the lower right-hand corner of the screen, click the dockers «whale» icon, and in the pop up context menu choose «Switch to Windows containers…». The Dockers software immediately resolves for Windows users and asks you to create a Dev Environment.
https://stackoverflow.com/a/75105105/5555938
Docker Desktop 4.16.0
wsl -l -v
showed docker-desktop stucked in installing state:
C:WINDOWSsystem32>wsl -l -v NAME STATE VERSION * Alpine Stopped 2 docker-desktop-data Stopped 2 Ubuntu-22.04 Stopped 2 docker-desktop Installing 2
wsl --shutdown
solved the issue for me.
, simply go to your Notifications/System Tray area of Windows in the lower right-hand corner of the screen, click the dockers «whale» icon, and in the pop up context menu choose «Switch to Windows containers…». The Dockers software immediately resolves for Windows users and asks you to create a Dev Envir
I’m not 100% sure, but I believe all you did here was tell it to ignore your problem with WSL. This doesn’t help fix the actual issue.
I followed the instructions on how to install Docker Desktop. When I start it. It says Docker Desktop stopped and engine not started.
The Docker Diagnostics ID is:
1e031030-f54a-4944-af27-d0458a8d136b/20220602004010
I’m not sure on how to fix it. This is a new install of ubuntu 20.04 with only docker desktop installed.
asked Jun 2, 2022 at 0:30
JasonJason
1111 silver badge6 bronze badges
Have you check the dependencies on the Docker Desktop linux install pages? There are a few. Not least of which is that this only runs under gnome or KDE. Check your environment with:
echo $XDG_CURRENT_DESKTOP
I can’t help you further. I am using XFCE so its quite probable it wont work for me. Also, I have production code running in Docker and I reallly don’t want to mess with it.
answered Jun 2, 2022 at 12:18
Fixed this problem by enabling virtualization from the BIOS settings.
answered Jun 27, 2022 at 10:32
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
Docker failed to initialize docker desktop is shutting down
This is one of the headbanging issues when docker stops working with the error as per image -1
Solution:
Go to
C:Users{username}AppDataLocalDocker
C:Users{username}AppDataRoamingDocker
C:Users{username}AppDataRoamingDocker Desktop
I have made the username bold as it should be different for you as shared mine
Delete all those docker folders or rename them.
Then open Docker as run as administrator, It should create fresh folders and open smoothly without any error.
Or by any chance, it throws an error, try uninstalling the Docker and delete the folders from the Program Files folder too, as mentioned below. then download and install a specific version of docker required.
Get inside
C:Program Files
C:ProgramData
C:Program Files (x86)
Delete those docker folders or rename them.
After following the above steps, You should be able to run docker smoothly.
Durga Charan Ojhahttps://lifeonnetwork.com/
I am a proud Indian, proud father, a blogger,
Being in a profession as System administrator, my passion is troubleshooting computer issues, I do like sharing solutions through blogging making videos of solving issues.
Hi !
Time to share a weird experience on Windows 10 and Docker. Sometimes, usually after some Windows 10 update or even after a software installation, docker stop responding.
An typical error may look like this.
error during connect: This error may indicate that the docker daemon is not running.: Post http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/build?buildargs=%7B%7D&cachefrom=%5B%5D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile.amd64&labels=%7B%7D&memory=0&memswap=0&networkmode=default&rm=1&shmsize=0&t=noToday.azurecr.io%2FU%3A0.0.88-amd64&target=&ulimits=null&version=1: open //./pipe/docker_engine: The system cannot find the file specified.
From Visual Studio Code we get:
And it’s very weird. When I check the Docker desktop app, it’s stuck in the the STARTING state.
I can restart the docker desktop app, and I will still have the issue. As I said, weird.
I’m a handy man, so I decided to restart the docker service. Just 2 commands:
Net stop com.docker.service Net start com.docker.service
However, this does not solve the problem. And sometimes, even restarting Windows won’t fix the problem.
After some time, I found the root cause:
Somehow WSL was set to version 1 instead of version 2.
I’m not sure why, however the solution is super easy. Just run a command to set WSL to version 2 and then restart docker service.
wsl --set-default-version 2 Net stop com.docker.service Net start com.docker.service
If you are a visual person, this may look like this:
Important: you need to run these commands with Administrator privileges. So in a Windows Terminal world, this may also look like this. Right click on the Windows Terminal App, and click on “Run as administrator”.
Happy coding!
Greetings
El Bruno
More posts in my blog ElBruno.com.
¿Con ganas de ponerte al día?
En Lemoncode te ofrecemos formación online impartida por profesionales que se baten el cobre en consultoría:
- Si tienes ganas de ponerte al día con Front End (ES6, Typescript, React, Angular, Vuejs…) te recomendamos nuestros Máster Front End: https://lemoncode.net/master-frontend#inicio-banner
- Si te quieres poner al día en Backend (stacks .net y nodejs), te aconsejamos nuestro Bootcamp Backend: https://lemoncode.net/bootcamp-backend#bootcamp-backend/banner
- Y si tienes ganas de meterte con Docker, Kubernetes, CI/CD…, tenemos nuestro Bootcamp Devops: https://lemoncode.net/bootcamp-devops#bootcamp-devops/inicio