Docker Unexpected error

[Amulya2528]

Description

running engine: waiting for the VM setup to be ready: starting WSL engine: bootstrapping in the main distro: starting wsl-bootstrap: context canceled docker engine is not running.

Reproduce

1. run docker as administrator and its showing the above error.

Expected behavior

Docker engine should run

docker version

20.10.

docker info

did wsl --shutdown and restarted, even then got the same error.

Diagnostics ID

A300B799-05AD-44E7-ADB7-EB3BF6C757E4/20240425093032

Additional Info

No response

[hblovo]

Getting back to an old version might help because I just saw your problem recently based on the error information.

[interplexed]

For me this appeared after upgrading Docker Desktop to v4.29.0 (latest) on Windows 11 23H2 (22631.3447) within the last week. After the error message, re-running the program results in the same error message. Using task manager to shutdown all docker-related processes and re-run, appears to work.
FWIW, it feels like a timeout based on internet connection. I'm setting my laptop to hibernate with it's not-so-great VPN connection up... it's as if when I disconnect the VPN, Docker Desktop loads normally.
Diagnostics ID: 57D5AE4A-0D1B-4ABD-9746-CB4530A08E0D/20240428084301

[samir-puranik]

I am also experiencing the same issue. Diagnostics ID: 49DC9064-604D-494C-ACB0-236581DCA481/20240429165804

docker --version
Docker version 26.0.0, build 2ae903e

wsl --list
Windows Subsystem for Linux Distributions:
docker-desktop-data (Default)
docker-desktop

[samir-puranik]

Getting back to an old version might help because I just saw your problem recently based on the error information.

Tried this and confirming that this works. I uninstalled 4.29.0 and re-installed 4.28.0 and now it's working again

[liumudj]

回退到之前版本有效

[liumudj]

https://docs.docker.com/desktop/release-notes/#docker-desktop-community-2501

[romancristinel]

Disabling the auto start on system start (via Task Manager / Startup apps) for Docker Desktop fixed it for me .

[senina4]

This work for me:

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

Restart Docker Desktop

[xszefo]

@senina4 , it also works for me, thanks! :)

[smartercow]

This work for me:

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

Restart Docker Desktop

Same

[Glutamat42]

had the same problem.

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

didn't solve the problem for me, but downgrading to 4.28.0 did.

[senina4]

This work for me:

wsl --unregister docker-desktop

wsl --unregister docker-desktop-data

Restart Docker Desktop

Because you uninstall docker desktop (I guess).

[clairmont32]

I had a really hard time cleanly uninstalling 4.28.0 on Windows 11 Enterprise and subsequently installing 4.29.0.

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

worked for me!

[fathyelshemy]

I am also experiencing the same issue. Diagnostics ID: 49DC9064-604D-494C-ACB0-236581DCA481/20240429165804

docker --version
Docker version 26.0.0, build 2ae903e

wsl --list
Windows Subsystem for Linux Distributions:
docker-desktop-data (Default)
docker-desktop

thanks @samir-puranik it works for me

[floris-xlx]

wsl --unregister docker-desktop-data

works for me too, thanks b

[Glutamat42]

had the same problem.

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

didn't solve the problem for me, but downgrading to 4.28.0 did.

Could now solve it for me. Looks like i had some docker binaries installed in my main WSL Disto (potentially i installed them manually some time in the past, no idea) and they now caused problems. I am not sure if i actually had to do the unregister part, but these are the steps i used to fix the problem for me

• winget remove Docker.DockerDesktop
• in wsl: apt remove docker*
• wsl --unregister docker-desktop (docker-desktop-data was already deleted by uninstalling Docker Desktop)
• winget add Docker.DockerDesktop
• reboot
• after starting Docker Desktop the first time it told me something failed and I should do wsl --shutdown -> wsl --shutdown

now after the next start of DockerDesktop it seems to work

[senina4]

When I uninstall Docker desktop docker-desktop-data didnt remove

[fjh1997]

This work for me:

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

Restart Docker Desktop

warning！this will clean all your images and containers

[xelmirage]

I had a really hard time cleanly uninstalling 4.28.0 on Windows 11 Enterprise and subsequently installing 4.29.0.

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

worked for me!

works for me!

[xrzm]

这对我来说是工作：

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

重启 Docker Desktop

this work for me ,thanks

[nikosvil]

This work for me:

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

Restart Docker Desktop

Had the same issue on 4.32.0, those commands fixed it. Thanks!

[nikolausmoll]

This work for me:

wsl --unregister docker-desktop
wsl --unregister docker-desktop-data

Restart Docker Desktop

warning！this will clean all your images and containers yeah, I don't know why the warning is not part of the original post...

anyway, did not solve it for me for Docker Desktop 4.33.1 (162079) - have to start the Docker software manually, but that sucks.

[lorenrh]

4.34.0 has been released with a fix for this issue, more information o the release notes.

I'll be closing this issue, but if the problem persists please open a fresh issue!

[andreaswrife]

The issue persists.

Updated from 4.33.1, being plagued with the the #13806 error. Now with 4.34.0 I get this issue. #14034 Although the release notes indicate that this bug is fixed.

I have tried the wsl --unregister quickfix without success.

I am gonna play around with it a bit more, see if there is some setting I've changed..

[vaibhavPH]

4.34.0 has been released with a fix for this issue, more information o the release notes.

I'll be closing this issue, but if the problem persists please open a fresh issue!

not fixed for me even in docker desktop 4.3.4

[andrea-reale]

Hey all - thanks for reporting that the problem persists with 4.34. Unfortunately, the fix introduced in 4.34 had itself a bug. Please, take a look at for a possible workaround https://github.com/docker/for-win/issues/14294#issuecomment-2324427416.

Since this issue is now closed, please use #14294 for any further communication (and remember to include diagnostics!).