Open ghkgupta opened 1 month ago
CaptainPaella
commented
1 month ago Me and my colleagues are experiencing the exact same issue.
wsl -v on my workstation displays:
WSL version: 2.2.4.0 Kernel version: 5.15.153.1-2 WSLg version: 1.0.61 MSRDC version: 1.2.5326 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26091.1-240325-1447.ge-release Windows version: 10.0.22631.3737
WongSIuWing
commented
1 month ago Same issue, hope they fix it.
Lobo204
commented
1 month ago Yeah been getting the same thing since update.
uaianaluiza
commented
1 month ago I’ve found, but the following was successful for me:
Try the following:
Stop Docker Desktop Run the following command in your terminal wsl --unregister docker-desktop Run Docker Desktop again (Will recreate the distro) Note: I also start my Docker Desktop as Administrator each time, so you probably need to run your terminal/Powershell as Administrator like I did.
Hope this helps! It was what worked for me
WongSIuWing
commented
1 month ago I’ve found, but the following was successful for me:
Try the following:
Stop Docker Desktop Run the following command in your terminal wsl --unregister docker-desktop Run Docker Desktop again (Will recreate the distro) Note: I also start my Docker Desktop as Administrator each time, so you probably need to run your terminal/Powershell as Administrator like I did.
Hope this helps! It was what worked for me
This solution worked for me as well.
This work around is required each time the computer is shutdown. Even after you type in the command in the command prompt.
Suggest fix: The fix that solve the requirement on typing this command each time the computer is shut down and re-open.
evagibson
commented
1 month ago I tried running: bcdedit /enum | findstr -i hypervisorlaunchtype If you see hypervisorlaunchtype Off, then the hypervisor is disabled. To enable it run in an elevated powershell: bcdedit /set hypervisorlaunchtype Auto Then start docker-desktop as admin This worked for me.
arnowelzel
commented
1 month ago Having the same isue with Docker Desktop 4.32.0 and Windows 11 Pro x64 and I have to use wsl --unregister docker-desktop after every boot of Windows, otherwise I get the same error as described in this issue.
Output of wsl -v:
WSL version: 2.0.14.0
Kernel version: 5.15.133.1-1
WSLg version: 1.0.59
MSRDC version: 1.2.4677
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22621.674
TMinh25
commented
1 month ago I’ve found, but the following was successful for me:
Try the following:
Stop Docker Desktop Run the following command in your terminal wsl --unregister docker-desktop Run Docker Desktop again (Will recreate the distro) Note: I also start my Docker Desktop as Administrator each time, so you probably need to run your terminal/Powershell as Administrator like I did.
Hope this helps! It was what worked for me
+1 same issue but this could not save me ☹️☹️ wsl -v
Kernel version: 6.6.36.3-1
WSLg version: 1.0.63
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22635.3930docker --version
Docker version 27.0.3, build 7d4bcd8Edit: The error I got is: error spotted in wslbootstrap log: "[2024-07-19T08:11:59.966916143Z][wsl-bootstrap][F] exit status 32"
WongSIuWing
commented
1 month ago ammend my wsl version here for inspection
WSL version: 2.1.5.0
Kernel version: 5.15.146.1-2
WSLg version: 1.0.60
MSRDC version: 1.2.5105
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp
Windows version: 10.0.22631.3880And the docker version
Docker version 27.0.3, build 7d4bcd8
drdogbot7
commented
1 month ago Same issue here I think, and wsl --unregister docker-desktop doesn't fix it.
The only way I can get docker to start is by unchecking "Use the WSL 2 based engine"… but then it doesn't work in WSL so not very helpful.
Docker Desktop 4.32.0
WSL version: 2.3.11.0
Kernel version: 6.6.36.3-1
WSLg version: 1.0.63
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22635.3930Update: My solution was to uninstall Docker Desktop and install Docker CE within WSL2. Using a fresh install of Ubuntu 24.04, this actually worked without much fuss. Much easier than it used to be: Add the docker repos, install the packages, add yourself to the "docker" group. A lot of the instructions online list several extra steps (like installing Compose) that aren't necessary anymore.
For me the advantage of Docker Desktop has always been that it "just works", but after wasting a whole day trying to fix this issue, that is certainly no longer the case.
arnowelzel
commented
1 month ago Maybe it helps anyone:
I finally managed to get it running again this way:
On the way WSL2 complained that wsl --update is not possible (required by Docker Desktop) because a component was already installed. By inspecting the Windows event log of the install AppXDeployment-Server I could identify the package name of WSL2 which had to be removed using Remove-AppxPackage -Package <package-name> -AllUsers. Then it was also possible to run wsl --update and finally get Docker Desktop 4.32.0 running as well.
JowaDev
commented
1 month ago Maybe it helps anyone:
I finally managed to get it running again this way:
Completely uninstall Docker Desktop, Ubuntu, WSL2
Reinstalling everything in the reverse order: first WSL2, then the WSL Linux kernel update, then Ubuntu, then Docker Desktop.
On the way WSL2 complained that
wsl --updateis not possible (required by Docker Desktop) because a component was already installed. By inspecting the Windows event log of the install ApoXDeployment-Server I could identify the package name of WSL2 which had to be removed usingRemove-AppxPackage -Package <package-name> -AllUsers. Then it was also possible to runwsl --updateand finally get Docker Desktop 4.32.0 running as well.
I have done the same way and finally working 👌🏽
djarami726
commented
1 month ago I’ve found, but the following was successful for me:
Try the following:
Stop Docker Desktop Run the following command in your terminal wsl --unregister docker-desktop Run Docker Desktop again (Will recreate the distro) Note: I also start my Docker Desktop as Administrator each time, so you probably need to run your terminal/Powershell as Administrator like I did.
Hope this helps! It was what worked for me
Having the same issue. Workaround only worked after I ran it from admin powershell and I also was launching docker desktop as admin as well.
Please fix this - this is so unproductive.
danperrout
commented
4 weeks ago When I logged in with an admin account, mine started working. "Run as Admin" did nothing with a default account.
Windows 11 Home here.
outerkatza
commented
3 weeks ago I have the same problem, I updated from 4.29 to 4.33,the same error happened.
WSL version: 2.1.5.0 Kernel version: 5.15.146.1-2 WSLg version: 1.0.60 MSRDC version: 1.2.5105 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22631.3880
Spongman
commented
3 weeks ago I get this error when starting:
error spotted in wslbootstrap log: "[2024-07-30T17:22:23.653841800Z][wsl-bootstrap][F] mounting /usr/lib/wsl to /tmp/docker-desktop-<USER>/usr/lib/wsl: no such file or directory"it was working fine yesterday, and i didn't change anyting. wtf.
mrxra
commented
1 week ago same issue here unfortunately. ran wsl --update which worked fine, reinstalled docker desktop, but didn't help. reverted back to version 4.29 for now :-(
djarami726
commented
1 week ago wsl --unregister docker-desktop stopped working for me. I then tried the uninstall Docker and reinstalled it - that worked for me.
cli-ish
commented
1 week ago This works for me:
cmd.exe as Adminwsl --unregister docker-desktopHope this gets fixed in the next update, i did not update wsl or anything just received an Docker Desktop update and since then i cant access it directly without the above steps.
Nereg
commented
1 week ago wsl --unregister docker-desktop stopped working for me. I then tried the uninstall Docker and reinstalled it - that worked for me.
Same here for me. Docker version 4.33.1, wsl -v:
WSL version: 2.2.4.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.19045.4780Diagnostics ID: 4B510FFD-ACCE-49E7-8D62-CDD8C2365975/20240816162020 The error message:
deploying WSL2 distributions
ensuring main distro is deployed: deploying "docker-desktop": importing WSL distro "Insufficient system resources exist to complete the requested service. \r\nError code: Wsl/Service/RegisterDistro/CreateVm/HCS/0x800705aa\r\n" output="docker-desktop": exit code: 4294967295: running WSL command wsl.exe C:\Windows\System32\wsl.exe --import docker-desktop <HOME>\AppData\Local\Docker\wsl\main C:\Program Files\Docker\Docker\resources\wsl\wsl-bootstrap.tar --version 2: Insufficient system resources exist to complete the requested service.
Error code: Wsl/Service/RegisterDistro/CreateVm/HCS/0x800705aa
: exit status 0xffffffff
checking if isocache exists: CreateFile \\wsl$\docker-desktop-data\isocache\: The network name cannot be found.Removing the wsl image doesn't help, although restarting does
D1yt
commented
3 days ago Most likely related to this patch: 4.30.0 For Windows Added a simplified provisioning mode for WSL2 that avoids the need for the ancillary docker-desktop-data WSL distribution (experimental).
Then this known bug: For Windows When upgrading to Docker Desktop 4.31.0, existing containers, images and volumes become invisible for users that created those containers and images using Docker Desktop 4.8.0 or lower, on Windows hosts with WSL only. The data is not lost, it just becomes invisible to Docker Desktop 4.31.0. If impacted, downgrade to version 4.30 or earlier. For more information see: docker/for-win#14118
And then this patch: 4.31.1 For Windows Fixed a bug where containers, images and volumes created before the update were potentially invisible for users. Fixes docker/for-win#14118
After backing up my 'DockerDesktopWSL' folder in a save location and a clean reinstall of WSL + Ubuntu + Docker Desktop and a few restarts, I had to: 1) quit Docker-Desktop and shutdown WSL 2) rename the 'data' folder to 'disk' in my 'DockerDesktopWSL' folder. 3) rename 'ext4.vhdx' to '' in my renamed 'disk' folder.
Would have liked to choose a better way of backing up, but that wasn't easy due to Docker-engine not being able to startup. Reminder to not auto-update software in production.
Description
Yesterday, my docker desktop was upgraded to 4.32.0. After upgradation, i started receiving the following error when starting it.
The problem persists even after several restarts.
_deploying WSL2 distributions ensuring main distro is deployed: checking if main distro is up to date: checking main distro bootstrap version: getting main distro bootstrap version: open \wsl$\docker-desktop\etc\wsl_bootstrapversion: The network name cannot be found. checking if isocache exists: CreateFile \wsl$\docker-desktop-data\isocache\: The network name cannot be found.
Reproduce
Expected behavior
docker desktop should run as usual without any errors.
docker version
docker info
Diagnostics ID
6DA45DCB-085F-4AB8-87AC-A9C14FA4C34E/20240710153213
Additional Info
Edition Windows 11 Pro Version 23H2 Installed on 03/06/2024 OS build 22631.3737 Experience Windows Feature Experience Pack 1000.22700.1009.0
wsl --statusDefault Distribution: Ubuntu Default Version: 2wsl -vWSL version: 2.2.4.0 Kernel version: 5.15.153.1-2 WSLg version: 1.0.61 MSRDC version: 1.2.5326 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.26091.1-240325-1447.ge-release Windows version: 10.0.22631.3737Note: I always use admin account to start the docker desktop