Docker Engine Failed to Start : Getting Error "waiting for docker daemon: running wsl-bootstrap: WSL engine terminated abruptly"

Chenthilraj commented 1 year ago

Description

Using Windows 10 Enterprise. Installed Docker Desktop for Windows and followed the instructions. It was running good. Suddenly, Getting this error : waiting for docker daemon: running wsl-bootstrap: WSL engine terminated abruptly

I tried the following

wsl --update to check Windows Subsystem for Linux is up todate
Thank you for contacting Docker Support. It may be worth initially trying to run a wsl --update to ensure you are using the latest version of WSL, but in order to troubleshoot further we'll need to look at the logfiles. Following this link you can run the diagnostics (even through terminal if Docker Desktop isn't starting) https://docs.docker.com/desktop/troubleshoot/overview/#diagnose-and-feedback

When it finishes the tests let us know the diagnostics ID

You might also try doing a clean re-install by clearing old files/folders. If it's still running into the issue after that you can do the diagnostics again and share the new diagnostics ID, so the logs are very concise for troubleshooting the issue.

Uninstall Docker Desktop
Deleted the below files: C:\ProgramData\Docker C:\ProgramData\DockerDesktop C:\Program Files\Docker C:\Users\\.docker C:\Users\\AppData\Local\Docker C:\Users\\AppData\Roaming\Docker C:\Users\\AppData\Roaming\Docker Desktop
Reinstalled Docker Desktop.

But still getting the same error.

Please find attached the docker diagnostic log files and report..

self-diagnose.txt

log.txt diagnostics.log log.txt self-diagnose.txt diagnostics.log

Reproduce

Install Docker Desktop for Windows
Use WSL
On starting the docker engine, getting this error.

Expected behavior

The docker engine should start without any issues

docker version

Since docker engine is not running unable to get this details. Using the latest version of Docker Desktop for Windows.

docker info

Since docker engine is not running unable to get this details. Using the latest version of Docker Desktop for Windows.

Diagnostics ID

6F238ACD-1ADD-4F16-8CAC-FC3E669EB7AE/20230808102434

Additional Info

NA

bsousaa commented 1 year ago

Can you try wsl --update and restart?

Chenthilraj commented 1 year ago

I tried wsl --update and wsl restart. Got the following output: PS C:\Program Files\Docker\Docker\resources> wsl --update Checking for updates. The most recent version of Windows Subsystem for Linux is already installed. PS C:\Program Files\Docker\Docker\resources> wsl restart

<3>WSL (338) ERROR: CreateProcessParseCommon:789: Failed to translate C:\Program Files\Docker\Docker\resources <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Windows\system32 <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Windows <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Windows\System32\Wbem <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Windows\System32\WindowsPowerShell\v1.0\ <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Windows\System32\OpenSSH\ <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Program Files (x86)\Riverbed\Steelhead Mobile\ <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Program Files\1E\Client\Extensibility\NomadBranch <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Program Files (x86)\Common Files\Hitachi ID\ <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Program Files\Common Files\Hitachi ID\ <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\home\nodejs\ <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\ProgramData\chocolatey\bin <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Program Files\Docker\Docker\resources\bin <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Users\BK335PS\AppData\Local\Microsoft\WindowsApps <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\tools\ide\VSCode\bin <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\tools\ide\PyCharmCE2023.1.3\bin <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\tools\ide\IntelliJCE2023.1.3\bin <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Users\BK335PS\AppData\Roaming\npm <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\tools\Git\cmd Failed to mount C:\, see dmesg for more details. /bin/bash: line 1: restart: command not found wsl --update returns response stating that a recent version is being used. Whereas wsl restart is throwing error.

Chenthilraj commented 1 year ago

I tried wsl --update and wsl restart. Got the following output: PS C:\Program Files\Docker\Docker\resources> wsl --update Checking for updates. The most recent version of Windows Subsystem for Linux is already installed. PS C:\Program Files\Docker\Docker\resources> wsl restart

<3>WSL (338) ERROR: CreateProcessParseCommon:789: Failed to translate C:\Program Files\Docker\Docker\resources <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Windows\system32 <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Windows <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Windows\System32\Wbem <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Windows\System32\WindowsPowerShell\v1.0 <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Windows\System32\OpenSSH <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Program Files (x86)\Riverbed\Steelhead Mobile <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Program Files\1E\Client\Extensibility\NomadBranch <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Program Files (x86)\Common Files\Hitachi ID <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Program Files\Common Files\Hitachi ID <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\home\nodejs <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\ProgramData\chocolatey\bin <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Program Files\Docker\Docker\resources\bin <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Users\BK335PS\AppData\Local\Microsoft\WindowsApps <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\tools\ide\VSCode\bin <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\tools\ide\PyCharmCE2023.1.3\bin <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\tools\ide\IntelliJCE2023.1.3\bin <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\Users\BK335PS\AppData\Roaming\npm <3>WSL (338) ERROR: UtilTranslatePathList:2803: Failed to translate C:\tools\Git\cmd Failed to mount C:, see dmesg for more details. /bin/bash: line 1: restart: command not found wsl --update returns response stating that a recent version is being used. Whereas wsl restart is throwing error. Thanks and Regards, Chenthilraj On Tue, Aug 8, 2023 at 4:06 PM Bruno Sousa ***@***.***> wrote: > Can you try wsl --update and restart? > > — > Reply to this email directly, view it on GitHub > , > or unsubscribe > > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

p1-0tr commented 1 year ago

Hi @Chenthilraj , could you try this build https://desktop-stage.docker.com/win/main/amd64/117973/Docker%20Desktop%20Installer.exe and let me know if it resolves the issue?

Chenthilraj commented 1 year ago

I tried downloading the installer, installed after uninstalling the existing version and cleaned up docker folders. When I execute docker desktop, After getting started, in a second or 2 it stopped with an error message "Unable to calculate image disk size"

In the terminal when I execute docker version, I am getting error like this request returned Internal Server Error for API route and version http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/version, check if the server supports the requested API version

For docker ps

error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json": open //./pipe/docker_engine: The system cannot find the file specified.*

Thanks and Regards, Chenthilraj

On Thu, Aug 10, 2023 at 2:07 PM Piotr @.***> wrote:

Hi @Chenthilraj https://github.com/Chenthilraj , could you try this build https://desktop-stage.docker.com/win/main/amd64/117973/Docker%20Desktop%20Installer.exe and let me know if it resolves the issue?

— Reply to this email directly, view it on GitHub https://github.com/docker/for-win/issues/13638#issuecomment-1672801265, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5ZGGCURIS3QK5PISY6ZW3XUSMWBANCNFSM6AAAAAA3IIFAVE . You are receiving this because you were mentioned.Message ID: @.***>

p1-0tr commented 1 year ago

@Chenthilraj thanks for giving that build a go could you gather diagnostics for it (https://docs.docker.com/desktop/troubleshoot/overview/#diagnose-from-the-terminal)?

PS Have you tried running wsl --shutdown and or rebooting your machine?

Chenthilraj commented 1 year ago

I gathered and uploaded the diagnostics. The diagnostic id is 562D1B40-9563-4A2A-8401-6779A27177DC/20230810151545 (uploaded)

Thanks and Regards, Chenthilraj

On Thu, Aug 10, 2023 at 6:58 PM Piotr @.***> wrote:

@Chenthilraj https://github.com/Chenthilraj thanks for giving that build a go could you gather diagnostics for it ( https://docs.docker.com/desktop/troubleshoot/overview/#diagnose-from-the-terminal )?

— Reply to this email directly, view it on GitHub https://github.com/docker/for-win/issues/13638#issuecomment-1673227408, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5ZGGHCPVZWAYHKJR7QVKDXUTOYFANCNFSM6AAAAAA3IIFAVE . You are receiving this because you were mentioned.Message ID: @.***>

p1-0tr commented 1 year ago

hi @Chenthilraj , the build I linked previously avoids sharing PATH between windows and WSL, which was aimed to work around Failed to translate errors coming from WSL. However I missed previously that those come about because WSL can't mount the C drive, rather than because there is some malformed entry on the PATH.

I assume you are also unable to run any commands in a regular WSL distro, e.g. wsl -d Ubuntu bash. One thing you could try doing about this is to restart the WSL service e.g. sc.exe stop wslservice and sc.exe start wslservice, after that check if you can successfully run wsl -d Ubuntu bash and DD. If that does not help you may need to file a WSL issue - https://github.com/microsoft/WSL .

ctalledo commented 1 year ago

because WSL can't mount the C drive

FYI we had another user report a similar issue, and in that case it turned out the user had a security app installed on their host (BeyondTrust) that had blocked C drive mounts into WSL distros. This in turn prevented Docker Desktop from starting on WSL, as it relies on that mount in order to setup the docker-desktop WSL distro.

I am not sure if this is the case here (@Chenthilraj can confirm), but thought I would mention it just in case.

cbruce80 commented 1 year ago

because WSL can't mount the C drive

FYI we had another user report a similar issue, and in that case it turned out the user had a security app installed on their host (BeyondTrust) that had blocked C drive mounts into WSL distros. This in turn prevented Docker Desktop from starting on WSL, as it relies on that mount in order to setup the docker-desktop WSL distro.

@ctalledo I am experiencing issues starting the Docker Engine with WSL2 and have Beyond Trust deployed on my machine. Were you able to find a workaround?

Chenthilraj commented 1 year ago

Hi,

Yes I have Beyond Trust deployed on my machine. What is the workaround?

Thanks and Regards, Chenthilraj

On Wed, Oct 4, 2023 at 9:46 PM Cameron Bruce @.***> wrote:

because WSL can't mount the C drive

FYI we had another user report a similar issue, and in that case it turned out the user had a security app installed on their host (BeyondTrust) that had blocked C drive mounts into WSL distros. This in turn prevented Docker Desktop from starting on WSL, as it relies on that mount in order to setup the docker-desktop WSL distro.

@ctalledo https://github.com/ctalledo I am experiencing issues starting the Docker Engine with WSL2 and have Beyond Trust deployed on my machine. Were you able to find a workaround?

— Reply to this email directly, view it on GitHub https://github.com/docker/for-win/issues/13638#issuecomment-1747234222, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5ZGGHUVG4LTX5PERXKAKTX5WDW3AVCNFSM6AAAAAA3IIFAVGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBXGIZTIMRSGI . You are receiving this because you were mentioned.Message ID: @.***>

ctalledo commented 12 months ago

Hi @cbruce80, @Chenthilraj,

We don't have a work-around at this point, other than a Docker customer saying they were able to work-around it by changing a BeyondTrust policy (though no details were provided). We will reach out to BeyondTrust to find out more.

In the meantime, if you find the solution please post it too. Thanks!

adrastus1025 commented 8 months ago

Hi @cbruce80 ,

I have the same issues today.

If you find the solution, please help me.

DgithubA commented 8 months ago

its happend to me right now after try git clone https://github.com/docker/multi-container-app docker compose up -d [im begginer] pleace help me

cbruce80 commented 8 months ago

Hi all,

I ended up having to reinstall Windows 11, but everything worked after that.

ailegion commented 7 months ago

Hi all,

I don't know if it's any help but I faced the same issue during an import of large file into container. The issue was resolved after I restarted WSL and immediately deleted the container that caused the issue in the first place. Everything seems to be working fine now. While the "bad container" was there WSL would terminate randomly and abruptly.

vgsyrov commented 7 months ago

I have the same issue. I tried to reinstall docker and wls (three time each) and have the same result (no results).

kkm commented 7 months ago

+1 Windows 11 only.

TinChung41 commented 6 months ago

+1 Windows 11 only.

+2 Window 11

umarbutler commented 6 months ago

+3 Windows 11

umarbutler commented 6 months ago

          I solved this issue by running

wsl --list,

and then wsl --unregister Ubuntu wsl --unregister docker-desktop wsl --unregister docker-desktop-data

and reinstall ubuntu by using wsl --install, restart your computer and start Docker, it should work.

Originally posted by @Robin-Lai-YY in https://github.com/docker/for-win/issues/13842#issuecomment-1899435510

vgsyrov commented 5 months ago

          I solved this issue by running 
wsl --list,

and then wsl --unregister Ubuntu wsl --unregister docker-desktop wsl --unregister docker-desktop-data

and reinstall ubuntu by using wsl --install, restart your computer and start Docker, it should work.

Originally posted by @Robin-Lai-YY in #13842 (comment)

I've tried this - don't work for me

AndreSiemens commented 5 months ago

I've tried this - don't work for me

It didn't work for me either 😐

PatricNox commented 5 months ago

Can you try wsl --update and restart?

I updated to Windows 11 and this issue started for me. However, following this quoted post, it then works thankfully! <3

vgsyrov commented 4 months ago

I've updated DockerDesktop and wsl - and it works

Abdelhamid-p0 commented 3 months ago

Some one had a solution for this Error:

error spotted in wslbootstrap log: "[2024-07-03T14:48:28.609763759Z][wsl-bootstrap][F] exit status 32"

Starstrike commented 3 months ago

Some one had a solution for this Error:

error spotted in wslbootstrap log: "[2024-07-03T14:48:28.609763759Z][wsl-bootstrap][F] exit status 32"

Did you happen to update the WSL2 kernel to 6.6? I just did that and got this error. Had to remove the kernel line from the .wslconfig in order for Docker to start properly. Seems Docker isn't compatible with this yet.

shalimujiang commented 3 months ago

Some one had a solution for this Error:有人针对此错误提出了解决方案： error spotted in wslbootstrap log: "[2024-07-03T14:48:28.609763759Z][wsl-bootstrap][F] exit status 32"wslbootstrap 日志中发现错误：“[2024-07-03T14:48:28.609763759Z][wsl-bootstrap][F] 退出状态 32”

Did you happen to update the WSL2 kernel to 6.6? I just did that and got this error. Had to remove the kernel line from the .wslconfig in order for Docker to start properly. Seems Docker isn't compatible with this yet.您是否碰巧将 WSL2 内核更新到了 6.6？我刚刚这样做并收到此错误。必须从 .wslconfig 中删除内核行才能使 Docker 正常启动。 Docker 似乎还不兼容这个。

Yes, I also tried updating WSL2 to version 6.6 today and found that it caused the error mentioned above. Clip_2024-07-04_12-43-40

KrishnaChaitanya45 commented 3 months ago

          I solved this issue by running 
wsl --list,

and then wsl --unregister Ubuntu wsl --unregister docker-desktop wsl --unregister docker-desktop-data

and reinstall ubuntu by using wsl --install, restart your computer and start Docker, it should work.

Originally posted by @Robin-Lai-YY in #13842 (comment)

This worked for me, thanks 🙌

inoyakaigor commented 2 months ago

The same issue. Diagnostics ID E27C29D7-DD49-4D8B-B35E-198FD7BCD8FC/20240711144222

error spotted in wslbootstrap log: "[2024-07-11T14:42:09.946922271Z][wsl-bootstrap][F] context canceled"

Related events from Windows Event log Restart of docker engine.zip Hyper-V logs.zip

AzureZeng commented 2 months ago

Some one had a solution for this Error: error spotted in wslbootstrap log: "[2024-07-03T14:48:28.609763759Z][wsl-bootstrap][F] exit status 32"

Did you happen to update the WSL2 kernel to 6.6? I just did that and got this error. Had to remove the kernel line from the .wslconfig in order for Docker to start properly. Seems Docker isn't compatible with this yet.

Yup, but earlier versions of Docker Desktop support custom kernel till v4.29

prova commented 2 months ago

Same problem here with kernel 6.6. Also, reverted back to 4.29.0 and it fails as well.

AzureZeng commented 2 months ago

Tested on WSL 2.3.11 with built-in Linux Kernel v6.6.36, not working

wgetnz commented 2 months ago

Tested on WSL 2.3.11 with built-in Linux Kernel v6.6.36, not working

+1

TheBestPessimist commented 2 months ago

I have the same issue.

Docker version 4.32.

Diagnostics ID:

6F4F3791-CDCE-4E01-B997-B05FAFC1EC52/20240718084224

Error:

error spotted in wslbootstrap log: "[2024-07-18T08:41:11.083126024Z][wsl-bootstrap][F] mounting /usr/lib/wsl to /tmp/docker-desktop-<USER>/usr/lib/wsl: no such file or directory"

After reverting to Docker 4.29, everything works

inoyakaigor commented 2 months ago

Gentlemen's I think I found the ~~error~~ possible solution. I have two work laptops with Windows 11 23h2, the same build 22631.3810 One is my old and the second is the new with fresh installed windows. wsl --version shows the same for both:

Версия WSL: 2.2.4.0
Версия ядра: 5.15.153.1-2 <-- kernel
Версия WSLg: 1.0.61
Версия MSRDC: 1.2.5326
Версия Direct3D: 1.611.1-81528511
Версия DXCore: 10.0.26091.1-240325-1447.ge-release
Версия Windows: 10.0.22631.3810

Docker 4.31.1 and 4.32.0 both had problems with start. At new computer I haven't any problems but at old one I have problems with Docker engine. Main difference was at old machine I have a .wslconfig file: %USERPROFILE%\.wslconfig with these content:

[wsl2]
kernelCommandLine=ipv6.disable=1
networkingMode=mirrored

[experimental]
hostAddressLoopback=true

I renamed it to .wslconfig.bak and Docker just started! Build and run container was succesfull. Then I stopped Docker, renamed back to .wslconfig and then again run Docker desktop and it has started succesfully. Hope it helps

wgetnz commented 2 months ago

Gentlemen's I think I found the ~error~ possible solution. I have two work laptops with Windows 11 23h2, the same build 22631.3810 One is my old and the second is the new with fresh installed windows. wsl --version shows the same for both:
Версия WSL: 2.2.4.0
Версия ядра: 5.15.153.1-2 <-- kernel
Версия WSLg: 1.0.61
Версия MSRDC: 1.2.5326
Версия Direct3D: 1.611.1-81528511
Версия DXCore: 10.0.26091.1-240325-1447.ge-release
Версия Windows: 10.0.22631.3810
Docker 4.31.1 and 4.32.0 both had problems with start. At new computer I haven't any problems but at old one I have problems with Docker engine. Main difference was at old machine I have a .wslconfig file: %USERPROFILE%\.wslconfig with these content:
[wsl2]
kernelCommandLine=ipv6.disable=1
networkingMode=mirrored

[experimental]
hostAddressLoopback=true
I renamed it to .wslconfig.bak and Docker just started! Build and run container was succesfull. Then I stopped Docker, renamed back to .wslconfig and then again run Docker desktop and it has started succesfully. Hope it helps

My problem is Linux Kernel v6.6.36, not working, downgrading it will fix it. I hope the kernel version problem can be solved

eapotapov commented 2 months ago

The reason for the problem with the 6.6 kernel is explained in this issue: https://github.com/microsoft/WSL/issues/11742

The issue arises because the upcoming version of WSL is going to support module autoload. As a result, Microsoft has moved many flags in the kernel config to be compiled as modules ("=m") instead of being built-in ("=y").

For custom-built kernels, module autoload is not working, which causes Docker Desktop to miss certain kernel features.

In the mentioned issue, I've posted a gist with the 6.6 kernel configuration, highlighting the "=y" flags that were changed to "=m" compared to 5.15.

I've tested this configuration, and it seems to be working. However, I will confirm its reliability after using it for a week or so.

wgetnz commented 2 months ago

The reason for the problem with the 6.6 kernel is explained in this issue: microsoft/WSL#11742

The issue arises because the upcoming version of WSL is going to support module autoload. As a result, Microsoft has moved many flags in the kernel config to be compiled as modules ("=m") instead of being built-in ("=y").

For custom-built kernels, module autoload is not working, which causes Docker Desktop to miss certain kernel features.

In the mentioned issue, I've posted a gist with the 6.6 kernel configuration, highlighting the "=y" flags that were changed to "=m" compared to 5.15.

I've tested this configuration, 和 it seems to be working. However, I will confirm its reliability after using it for a week or so.

Thanks, I will try it

wgetnz commented 2 months ago

The reason for the problem with the 6.6 kernel is explained in this issue: microsoft/WSL#11742

The issue arises because the upcoming version of WSL is going to support module autoload. As a result, Microsoft has moved many flags in the kernel config to be compiled as modules ("=m") instead of being built-in ("=y").

For custom-built kernels, module autoload is not working, which causes Docker Desktop to miss certain kernel features.

In the mentioned issue, I've posted a gist with the 6.6 kernel configuration, highlighting the "=y" flags that were changed to "=m" compared to 5.15.

I've tested this configuration, and it seems to be working. However, I will confirm its reliability after using it for a week or so.

It worked.

eapotapov commented 2 months ago

The reason for the problem with the 6.6 kernel is explained in this issue: microsoft/WSL#11742 The issue arises because the upcoming version of WSL is going to support module autoload. As a result, Microsoft has moved many flags in the kernel config to be compiled as modules ("=m") instead of being built-in ("=y"). For custom-built kernels, module autoload is not working, which causes Docker Desktop to miss certain kernel features. In the mentioned issue, I've posted a gist with the 6.6 kernel configuration, highlighting the "=y" flags that were changed to "=m" compared to 5.15. I've tested this configuration, and it seems to be working. However, I will confirm its reliability after using it for a week or so.

It worked.

Glad that it helped!

For everyone trying kernel 6.6: I think fundamentally, there's no bug in Docker Desktop to fix (though better error reporting in such cases might be helpful).

As of now (July 22nd, 2024), the 6.6 kernel configuration provided by Microsoft cuts out a lot of kernel features (by moving them to modules), including those required by Docker.

I hope they will either enable autoloading for custom kernel builds or revert the configuration to have features built-in.

johanbx commented 2 months ago

Hum... I had some issues with docker desktop as well on Windows 11.

What finally worked was shut down docker for desktop, run wsl --install, and then start docker for desktop.

No idea why it just worked... maybe it added some missing configs or what not? The output from the wsl --install command just says "Ubuntu already installed. Starting Ubuntu..."

I got this:

wsl --version
WSL-version: 2.2.4.0
Kernelversion: 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.3880

Running docker desktop v4.32.0

Hope it helps someone else.

AzureZeng commented 2 months ago

Hum... I had some issues with docker desktop as well on Windows 11.

What finally worked was shut down docker for desktop, run wsl --install, and then start docker for desktop.

No idea why it just worked... maybe it added some missing configs or what not? The output from the wsl --install command just says "Ubuntu already installed. Starting Ubuntu..."

I got this:
wsl --version
WSL-version: 2.2.4.0
Kernelversion: 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.3880
Running docker desktop v4.32.0

Hope it helps someone else.

you are running WSL 2.2.4 / Linux kernel 5.15 which works perfectly with docker desktop

shuyih commented 2 months ago

Hum... I had some issues with docker desktop as well on Windows 11.

What finally worked was shut down docker for desktop, run wsl --install, and then start docker for desktop.

No idea why it just worked... maybe it added some missing configs or what not? The output from the wsl --install command just says "Ubuntu already installed. Starting Ubuntu..."

I got this:
wsl --version
WSL-version: 2.2.4.0
Kernelversion: 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.3880
Running docker desktop v4.32.0

Hope it helps someone else.

Is this your error?

I have uninstalled and reinstalled WSL2, Docker Desktop a few times, but this error persists.

error spotted in wslbootstrap log: "[2024-07-24T02:00:40.083465995Z][wsl-bootstrap][F] exec: \"mount\": executable file not found in $PATH"

johanbx commented 2 months ago

Hum... I had some issues with docker desktop as well on Windows 11.

What finally worked was shut down docker for desktop, run wsl --install, and then start docker for desktop.

No idea why it just worked... maybe it added some missing configs or what not? The output from the wsl --install command just says "Ubuntu already installed. Starting Ubuntu..."

I got this:
wsl --version

WSL-version: 2.2.4.0

Kernelversion: 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.3880
Running docker desktop v4.32.0

Hope it helps someone else.
Is this your error?

I have uninstalled and reinstalled WSL2, Docker Desktop a few times, but this error persists.

error spotted in wslbootstrap log: "[2024-07-24T02:00:40.083465995Z][wsl-bootstrap][F] exec: \"mount\": executable file not found in $PATH"

Yes I had that error! Not sure it matters, but I also removed my .wslconfig file (renamed it .wslconfig.bak)

I was just starting Ubuntu, shutting down wsl through the shutdown command, and restarted docker a few times, and then it finally worked after just running wsl --install.

So, in order: shutdown docker desktop Run wsl --shutdown Rename .wslconfig in user folder Run wsl --install Start docker desktop

prova commented 2 months ago

The kernel has now been auto-updated during the Insider Windows 11 build upgrade to 6.6.36.3-microsoft-standard-WSL2. I have now the latest Docker Desktop running with no changes and it seems all is good.

avbfr commented 2 months ago

I have the same issue.

Docker version 4.32.

Diagnostics ID:
6F4F3791-CDCE-4E01-B997-B05FAFC1EC52/20240718084224
Error:
error spotted in wslbootstrap log: "[2024-07-18T08:41:11.083126024Z][wsl-bootstrap][F] mounting /usr/lib/wsl to /tmp/docker-desktop-<USER>/usr/lib/wsl: no such file or directory"
After reverting to Docker 4.29, everything works

+1 (Windows 10 Enterprise)

Spongman commented 2 months ago

I have this error:

error spotted in wslbootstrap log: "[2024-07-30T17:56:34.491117392Z][wsl-bootstrap][F] mounting /usr/lib/wsl to /tmp/docker-desktop-/usr/lib/wsl: no such file or directory"