Docker Desktop - Unexpected WSL error

[Param2502]

Description

During opening of the Docker Desktop, it is throwing error and application is not starting. I tried multiple times by restarting my system as well.

provisioning docker WSL distros: ensuring main distro is deployed: deploying "docker-desktop": importing WSL distro "WSL2 is not supported with your current machine configuration.\r\nPlease enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS.\r\nEnable "Virtual Machine Platform" by running: wsl.exe --install --no-distribution\r\nFor information please visit https://aka.ms/enablevirtualization\r\nError code: Wsl/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED\r\n" output="docker-desktop": exit code: 4294967295: running WSL command wsl.exe C:\Windows\System32\wsl.exe --import docker-desktop \AppData\Local\Docker\wsl\distro C:\Program Files\Docker\Docker\resources\wsl\wsl-bootstrap.tar --version 2: WSL2 is not supported with your current machine configuration.
P

Reproduce

I just opened the Docker Desktop application and it is not starting.

Expected behavior

It should open.

docker version

docker desktop

docker info

docker desktop

Diagnostics ID

8CB7B499-8FF4-46E0-BE8D-DBD74AC14BBA/20240423023553

Additional Info

let me know when can i get help?

[voonyee]

Hi, based on the error you have shared, it would be good to check if your machine meets the below requirements:
https://docs.docker.com/desktop/install/windows-install/#system-requirements
https://docs.docker.com/desktop/troubleshoot/topics/#virtualization

[korkmazalper]

I also have a similar problem. I have been used normally for years in windows. After some value changes for the Linux subsystem, i began to receive a similar error. For a long time I could not find a solution.
My solution is as follows:

• uninstall the subsystem by wsl --uninstall
• reinstall wsl
• update docker to latest version: to set default settings
• reboot the machnien

[01fe22bca208]

provisioning docker WSL distros: getting WSL distro list: running WSL command wsl.exe C:\WINDOWS\System32\wsl.exe -l -v --all: context deadline exceeded
checking if isocache exists: CreateFile \wsl$\docker-desktop-data\isocache: The filename, directory name, or volume label syntax is incorrect.
ID:
28233483-9972-4116-BD77-4306658D9892/20240428155133

[SHWAKI]

HELLO GUYS I HAVE THIS PROBLEM ON DOCKER '97FB6776-6B27-4AC8-84C3-E2E459846A4E/20240429000308'
I HAVE NEVER USED IT BEFORE
CAN ANYONE HELP ??

[wlbragg]

Same problem here. Docker Desktop for Windows is broken. I have been using it for a year or so. I think maybe a Windows update broke it?

[colinasquith]

Reinstalling Docker fixed it for me, I think there was a mix-up in a WSL upgrade that left Docker in a strange state - reinstalling sorted everything out.

[sawich]

In my case, virtualization was disabled. This happened after flashing the bios.

[JoshuaIzu]

I also have the same issue
E9AB57F7-0383-421E-BEF2-DDFBE720085E/20240529103422

[wlbragg]

Reinstalling WSL and Docker Desktop did not fix it for me. I am still unable to use Docker Desktop. OIt is completely broken for me.

I start here with this error and now have progressed to this.
#14086

It's likely my fault, but I don't know enough to dig myself out of it.

[danyabsim]

I had the same one. After finding the solution to this error for a whole day, I found the answer in microsoft/WSL#7068 (comment) and it works.

[JoshuaIzu]

On Thu, 30 May 2024 at 7:37 AM, Daniel Baich ***@***.***> wrote: I had the same one. After finding the solution to this error for a whole day, I found the answer in microsoft/WSL#7068 (comment) and it works. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.

check if your Microsoft visualization is on that should solve the problem

…

[amg262]

I got this error on 4.32.0 upgrade and tried some things online with no success. What did work for me:

Try the following:

1. Stop Docker Desktop
2. Run the following command in your terminal wsl --unregister docker-desktop
3. Run Docker Desktop again (Will recreate the distro)

May need to run terminal/Powershell as Administrator. I had to, as I run Docker Desktop as an Administrator. But these steps worked for me

[strobelm]

I got this error on 4.32.0 upgrade and tried some things online with no success. What did work for me:

Try the following:

1. Stop Docker Desktop

2. Run the following command in your terminal wsl --unregister docker-desktop

3. Run Docker Desktop again (Will recreate the distro)

May need to run terminal/Powershell as Administrator. I had to, as I run Docker Desktop as an Administrator. But these steps worked for me

I can confirm that this worked for me, too. Thanks @amg262

[wlbragg]

Try the following:

1. Stop Docker Desktop
2. Run the following command in your terminal wsl --unregister docker-desktop
3. Run Docker Desktop again (Will recreate the distro)

Thank you so much for this info. It worked for me as well. I had to have docker desktop running for the unregister to be recognised and work. This was tricky at one point because my d desktop would fail and exit. So the second it opened and tried to init I executed the wsl unregister command and it worked.

[Antardas]

I got this error on 4.32.0 upgrade and tried some things online with no success. What did work for me:

Try the following:

1. Stop Docker Desktop
2. Run the following command in your terminal wsl --unregister docker-desktop
3. Run Docker Desktop again (Will recreate the distro)

May need to run terminal/Powershell as Administrator. I had to, as I run Docker Desktop as an Administrator. But these steps worked for me

@amg262 thanks. it's worked for me

[Reco1I]

I got this error on 4.32.0 upgrade and tried some things online with no success. What did work for me:

Try the following:

1. Stop Docker Desktop
2. Run the following command in your terminal wsl --unregister docker-desktop
3. Run Docker Desktop again (Will recreate the distro)

May need to run terminal/Powershell as Administrator. I had to, as I run Docker Desktop as an Administrator. But these steps worked for me

Working

[xDaveN]

Running into this issue on 4.32.0 aswell. Win 11 Pro.
Got virtualization enabled in BIOS and reinstalling WSL or Docker doesn't fix the issue.

Running wsl --unregister docker-desktop returns
There is no distribution with the supplied name. Error code: Wsl/Service/WSL_E_DISTRO_NOT_FOUND

Manually installing a distro by e.g. using wsl --install -d Ubuntu also returns
There is no distribution with the supplied name. Error code: Wsl/Service/WSL_E_DISTRO_NOT_FOUND

Virtual Machine Platform is also enabled in Windows. Also tried running everything as admin. Running out of ideas, lol.
My docker also randomly crashes sometimes when clicking through the settings.

I actually fixed it

I ran bcdedit /set hypervisorlaunchtype auto

I had previously installed an Android emulator which was incompatible with Hyper-V, so it force turned it off. Turning it on/off in windows settings didn't seem to affect it, but the command worked.

I also had to manually install a distro using wsl --install ubuntu and restart Docker as admin.

[cagataysen]

I had the same error, I have tried to reinstall docker, but didn't work again. Unfortunately, some of the command lines didn't work for me about unregistering the docker desktop which are above. So after enabling the virtualization on BIOS and restarting the computer it started to work. If you have Windows 10 or Windows 8 operating system, the easiest way to check is by opening up Task Manager->Performance Tab. You should see the Virtualization on the right down below as enabled. If it is enabled, it means that your CPU supports Virtualization and is currently enabled in BIOS. If it shows disabled, you need to enable it in BIOS. If you don’t see virtualization, your CPU does not support it.

Also, check these two links out:
Virtualization: https://docs.docker.com/desktop/troubleshoot/topics/#virtualization
Docker installing requirements: https://docs.docker.com/desktop/install/windows-install/

[clxseizetheday]

Running into this issue on 4.32.0 aswell. Win 11 Pro. Got virtualization enabled in BIOS and reinstalling WSL or Docker doesn't fix the issue.

Running wsl --unregister docker-desktop returns There is no distribution with the supplied name. Error code: Wsl/Service/WSL_E_DISTRO_NOT_FOUND

Manually installing a distro by e.g. using wsl --install -d Ubuntu also returns There is no distribution with the supplied name. Error code: Wsl/Service/WSL_E_DISTRO_NOT_FOUND

Virtual Machine Platform is also enabled in Windows. Also tried running everything as admin. Running out of ideas, lol. My docker also randomly crashes sometimes when clicking through the settings.

I actually fixed it

I ran bcdedit /set hypervisorlaunchtype auto

I had previously installed an Android emulator which was incompatible with Hyper-V, so it force turned it off. Turning it on/off in windows settings didn't seem to affect it, but the command worked.

I also had to manually install a distro using wsl --install ubuntu and restart Docker as admin.

you r damn right!!! I was handling this issue painfully, after I read your comment, I realized that your problem is caused by
the conflict between your Android emulator and your docker. I dont have Android emulator but I am using VMware. The principle of our issue is the same.

[judeVector]

I got this error on 4.32.0 upgrade and tried some things online with no success. What did work for me:

Try the following:

1. Stop Docker Desktop
2. Run the following command in your terminal wsl --unregister docker-desktop
3. Run Docker Desktop again (Will recreate the distro)

May need to run terminal/Powershell as Administrator. I had to, as I run Docker Desktop as an Administrator. But these steps worked for me

I can confirm that this also worked for me , thanks a lot for this . I have been reading and searching the web for solution

[KamiTzayig]

I actually fixed it

I ran bcdedit /set hypervisorlaunchtype auto

you saved me @xDaveN !

same problem with windows 11 and VirtualBox, force disabled hyper v and your solution fixed the problem

ran the command and restarted the computer, after that it was back to normal

[amg262]

I actually fixed it

I ran bcdedit /set hypervisorlaunchtype auto

you saved me @xDaveN !

same problem with windows 11 and VirtualBox, force disabled hyper v and your solution fixed the problem

ran the command and restarted the computer, after that it was back to normal

Interesting. your Docker Desktop working totally normally until 4.30.x or so, and then upon that update, you got this issue?

That's what I experienced, but I've been running that same command on reboot every time since.

[KamiTzayig]

@amg262 it worked normally until i force disabled hyper V. without a version change, not sure what version i was though

after the error, i tried a few things and then reinstalled docker desktop to the newest version, still didnt work.

so you say you need to run bcdedit /set hypervisorlaunchtype auto after every reboot? sheesh, hope its not my case

[amg262]

@amg262 it worked normally until i force disabled hyper V. without a version change, not sure what version i was though

after the error, i tried a few things and then reinstalled docker desktop to the newest version, still didnt work.

so you say you need to run bcdedit /set hypervisorlaunchtype auto after every reboot? sheesh, hope its not my case

I didn't force disable hyper-v, so my issue must be different. I have to run the unregister command I posted after every restart. Otherwise I get the same error

[j-tap]

1. Check if virtualization is enabled in BIOS
2. Check if Hyper-V is enabled in system components
3. Execute as Administrator dism.exe /online /enable-feature /featurename:VirtualMachinePlatform /all /norestart in Powershell
4. Reboot
5. Execute as Administrator wsl --install --no-distribution in Powershell

[ChrisilDavid28]

Same problem here. Docker Desktop for Windows is broken. I have been using it for a year or so. I think maybe a Windows update broke it?

Yeah I face this issue right after a Windows update.

[dave2nian]

last time, I upgraded VMware workstation from 16 to 17. due to one VM processor need to enable TV-x, I ran "bcdedit /set hypervisorlaunchtype off" . and than my Docker.Desktop gotten this problem.

to Fix:
I ran "bcdedit /set hypervisorlaunchtype auto“ and then turned off and on the Virtual machine Platform, the Windows Subsystem for Linux, the Windows Hypervisor Platform in CMD "optionalfeatures".
restart PC.

[joelsb9]

For me it was also the virtualization on BIOS.