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

[Chenthilraj]

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

1. wsl --update to check Windows Subsystem for Linux is up todate
2. 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.

1. Uninstall Docker Desktop

2. 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

3. 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

1. Install Docker Desktop for Windows
2. Use WSL
3. 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]

Can you try wsl --update and restart?

[Chenthilraj]

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]

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 https://github.com/docker/for-win/issues/13638#issuecomment-1669363851, or unsubscribe https://github.com/notifications/unsubscribe-auth/AC5ZGGEFYJ6B3O6Q3Y7YIZTXUIJDPANCNFSM6AAAAAA3IIFAVE . You are receiving this because you authored the thread.Message ID: @.***>

[p1-0tr]

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]

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]

@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]

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]

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]

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]

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]

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]

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]

Hi @cbruce80 ,

I have the same issues today.

If you find the solution, please help me.

[DgithubA]

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]

Hi all,

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

[ailegion]

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]

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

[kkm]

+1 Windows 11 only.

[TinChung41]

+1 Windows 11 only.

+2 Window 11

[umarbutler]

+3 Windows 11

[umarbutler]

          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]

          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]

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

It didn't work for me either 😐

[PatricNox]

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]

I've updated DockerDesktop and wsl - and it works

[Abdelhamid-p0]

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]

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]

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.

[KrishnaChaitanya45]

          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]

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