WSL 2.5.4 Breaks Docker Desktop for Windows - Will not start #12748

FlattusBlastus · 2025-03-27T06:53:20Z

Windows Version

Windows 11

WSL Version

2.5.4

Are you using WSL 1 or WSL 2?

WSL 2
WSL 1

Kernel Version

6.6 I guess

Distro Version

None

Other Software

No response

Repro Steps

Boot PC. DD fails to launches but the engine does not.

Expected Behavior

Boot PC. DD starts automatically.

Actual Behavior

DD fails to launches but the engine does not.

Diagnostic Logs

Just a heads up - moved back to 2.4.13 asap

github-actions · 2025-03-27T06:54:04Z

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

aepot · 2025-03-27T07:00:03Z

Same for Docker Desktop 4.39.0 + WSL 2.5.4 pre-release

Docker Engine shuts down with error:

running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine:
error spotted in wslbootstrap log: "[2025-03-26T16:59:21.508166733Z][wsl-bootstrap][F] context canceled"

The error pops up not every time. Not sure if it's connected to the issue directly.

C:\> wsl --version
WSL version: 2.5.4.0
Kernel version: 6.6.75.1-1
WSLg version: 1.0.66
MSRDC version: 1.2.6074
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26100.3194

# uname -a
Linux docker-desktop 6.6.75.1-microsoft-standard-WSL2 #1 SMP PREEMPT_DYNAMIC Sat Feb  8 02:00:20 UTC 2025 x86_64 Linux

Downgraded back to 2.5.1 pre-release, it works fine now.

UPD: I don't use .wslconfig, there's no such file in my profile.

justknife · 2025-03-27T08:41:06Z

I got the same error, and the fix was to add .wslconfig to the user's windows directory with the following parameters:

[boot]
systemd=true
[automount]
enabled=true
mountFsTab=true

Tristan-MyAnaPro · 2025-03-27T08:47:19Z

I just updated, have DD 4.39.0 and WSL 2.5.4.0 and I don't have any issue 🤔

Does the problem appear only when opening the session after a cold start or anytime DD tries to starts?

I got the same error, and the fix was to add .wslconfig to the user's windows directory with the following parameters:

[boot]
systemd=true
[automount]
enabled=true
mountFsTab=true

@justknife These are all already the same as the default values, so if you didn't had a .wslconfig file, it should not change anything (see https://learn.microsoft.com/fr-fr/windows/wsl/wsl-config#automount-settings)

justknife · 2025-03-27T08:48:40Z

I just updated, have DD 4.39.0 and WSL 2.5.4.0 and I don't have any issue 🤔

Does the problem appear only when opening the session after a cold start or anytime DD tries to starts?

I got the same error, and the fix was to add .wslconfig to the user's windows directory with the following parameters:

[boot]
systemd=true
[automount]
enabled=true
mountFsTab=true

@justknife These are all already the same as the default values, so if you didn't had a .wslconfig file, it should not change anything (see https://learn.microsoft.com/fr-fr/windows/wsl/wsl-config#automount-settings)

Before these parameters were explicitly declared, Docker crashed with errors similar to those seen by the users above.

alexey-us · 2025-03-28T07:36:03Z

Got same error:

WSL version: 2.5.4.0
Kernel version: 6.6.75.1-1
WSLg version: 1.0.66
MSRDC version: 1.2.6074
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26200.5510

If create .wslconfig and add strings written above, my wsl VM cuss at them :)

wsl -d docker-desktop
wsl: Unknown key 'automount.crossDistro' in /etc/wsl.conf:3

I have another one machine with Windows version 10.0.26120.1843, all other versions is same, all working fine

How to rollback to previous version?

auriz24 · 2025-03-28T08:47:09Z

Does the problem appear only when opening the session after a cold start or anytime DD tries to starts?

I'm experiencing the issue in both scenarios. The issue "Docker Engine stopped" is always present when launching Docker Desktop after having restarted the PC. Then, if I close/re-open Docker, I'd say it's 50/50 on whether the docker engine will start successfully or fail to start.

Docker Docker Desktop 4.39.0
WSL 2.5.4.0
Windows 11 24H2 Build 26100.3476

Edit: updated the findings

Tristan-MyAnaPro · 2025-03-28T09:06:30Z

If create .wslconfig and add strings written above, my wsl VM cuss at them :)
wsl -d docker-desktop
wsl: Unknown key 'automount.crossDistro' in /etc/wsl.conf:3

WSL raise an error in the event viewer about automount.crossDistro for me too since the 2.5.1 pre-release. It seems to only be a warning and never caused any problem on my side.

Does the problem appear only when opening the session after a cold start or anytime DD tries to starts?

I'm experiencing the issue in both scenarios. The issue "Docker Engine stopped" is always present when launching Docker Desktop after having restarted the PC. Then, if I close/re-open Docker, I'd say it's 50/50 on whether the docker engine will start successfully or fail to start.

Docker Docker Desktop 4.39.0 WSL 2.5.4.0 Windows 11 24H2 Build 26100.3476

That's weird...

My versions are:
WSL 2.5.4.0
Docker 4.39.0
Windows 24H2 (build 26100.3476)

I have docker desktop starting when I open my session and my WSL distro is Debian.

We seem to share the same versions on pretty much anything but I have no docker error! 🤔

I re-tried today with a cold boot, a reboot, shutting down and restarting docker without shutting down WSL, down and restarting docker after a wsl --shutdown... No error whatsoever...

I guess I can only wish you all a good luck 🤣

BTW, last time I had a serious problem with DD and WSL (no docker.sock was available in WSL), I had to uninstall Docker Desktop completely (which mean manually deleting files and folder in AppData and all following this doc : https://docs.docker.com/desktop/uninstall/ )

Maybe worth giving it a try? (It will delete any volume, container etc., make backups if you don't want to lose any data related to docker!)

alexey-us · 2025-03-28T11:01:41Z

Completely remove Docker and reinstall, no luck. Docker running and immediately stopped, tried Docker Desktop 4.38, instead 4.39

Update:
Remove Docker Desktop, WSL, Virtual Machine Platform feature, and current VM on Ubuntu 22.04, then re-install WSL by "wsl --install" with auto add Windows Features, add new distro Ubuntu 24.04. Then install Docker Desktop 4.38.0 (prev version) and all working fine.

After Docker start I have error "checking distro state for "Ubuntu-24.04": Get "http://ipc/check?distro=Ubuntu-24.04": context deadline exceeded: unexpected error", but Docker Desktop working fine

After update to latest Docker Desktop with no issue!

FlattusBlastus · 2025-03-29T21:26:26Z

running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2025-03-29T21:22:18.642773538Z][wsl-bootstrap][F] context canceled"

Reverting again

craigktreasure · 2025-03-31T22:21:52Z

I've reverted back to the stable builds (2.4.13.0) by running:

wsl --uninstall
wsl --install --no-distribution

Docker Desktop now starts just fine.

OneBlue · 2025-04-01T21:17:50Z

running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2025-03-29T21:22:18.642773538Z][wsl-bootstrap][F] context canceled"

Reverting again

@FlattusBlastus: Could you capture /logs of this failure ? That would help us understand what's causing this

ryanwinter · 2025-04-04T00:07:28Z

There are a lot of logs on the 2.5.1 thread: #12711

ryanwinter · 2025-04-04T00:46:27Z

I see the following error starting the VM:

[init                  ][E] FATAL: initializing TAP AF_VSOCK: opening tap interface: no such file or directory

Larger log:

[2025-04-04T00:35:22.240001700Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.240355737Z][init                  ] VM init started
[2025-04-04T00:35:22.240616900Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.240513641Z][init                  ] error mounting devtmpfs to /dev: device or resource busy
[2025-04-04T00:35:22.243263900Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.243218501Z][init                  ] added cpuset to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:35:22.243263900Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.243274006Z][init                  ] added cpu to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:35:22.243263900Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.243491448Z][init                  ] added io to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:35:22.243263900Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.243577265Z][init                  ] added memory to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:35:22.243796200Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.243594351Z][init                  ] added hugetlb to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:35:22.243849700Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.243692189Z][init                  ] added pids to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:35:22.243849700Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.243835811Z][init                  ] added rdma to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:35:22.253407300Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.253229384Z][init.socketforward    ] listening on virtual address: debug-socketforwarder
[2025-04-04T00:35:22.253407300Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.253272340Z][init.socketforward    ] listening on virtual address: perf-socketforwarder
[2025-04-04T00:35:22.253407300Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.253279797Z][init.socketforward    ] listening on virtual address: control-socketforwarder
[2025-04-04T00:35:22.253407300Z][com.docker.backend.exe.socketforward] [2025-04-04T00:35:22.253380068Z][vpnkit-bridge] /run/guest-services/socketforwarder-receive-fds.sock: successfully connected after 327.541906ms
[2025-04-04T00:35:22.271620000Z][com.docker.backend.exe.socketforward] [2025-04-04T00:35:22.271638870Z][vpnkit-bridge] sent fds so blocking forever
[2025-04-04T00:35:22.296349100Z][com.docker.backend.exe.WSLBootstrap] grep: /etc/securetty: No such file or directory
[2025-04-04T00:35:22.298968800Z][com.docker.backend.exe.WSLBootstrap] getty: cmdline has console=hvc0 but does not exist in /etc/securetty; will not be able to log in as root on this tty hvc0.
[2025-04-04T00:35:22.300021300Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.300243229Z][init.socketforward    ] listening on virtual address: control-init
[2025-04-04T00:35:22.300548900Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.300430328Z][init.gpio             ] no PL061 controller found
[2025-04-04T00:35:22.303779200Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.303629718Z][init.ipc              ] 23a2c89d-pause/unpause ->  
[2025-04-04T00:35:22.313941700Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.314236686Z][init                  ] platform has no virtio-net NICs
[2025-04-04T00:35:22.315008200Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.315228101Z][init                  ][E] FATAL: initializing TAP AF_VSOCK: opening tap interface: no such file or directory
[2025-04-04T00:35:22.315008200Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.315297201Z][init.poweroff         ] preparing to power the VM off...
[2025-04-04T00:35:22.318258800Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.318505356Z][init.poweroff         ] killing /usr/bin/bash (pid 38)
[2025-04-04T00:35:22.318258800Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.318608831Z][init.poweroff         ] killing /usr/bin/login (pid 39)
[2025-04-04T00:35:22.318793200Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.318847487Z][init                  ] reaped pid 38
[2025-04-04T00:35:22.318793200Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.319025090Z][init                  ] reaped pid 39
[2025-04-04T00:35:22.318793200Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.319185769Z][init.poweroff         ] all processes have shutdown
[2025-04-04T00:35:22.323559000Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.323396740Z][init.poweroff         ] disks synced
[2025-04-04T00:35:22.323559000Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.323443840Z][init.poweroff         ] VM is ready to be powered off
[2025-04-04T00:35:22.323559000Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.323452714Z][init.poweroff         ] flushing memlogd logs...
[2025-04-04T00:35:22.323559000Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.323457762Z][init.poweroff         ] flushing memlogd logs succeeded
[2025-04-04T00:35:22.323559000Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.323462436Z][init.poweroff         ] power the vm off
[2025-04-04T00:35:22.328812200Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:35:22.329020033Z][wsl-bootstrap] unshare caught expected signal interrupt

OneBlue · 2025-04-04T00:51:12Z

Thank you @ryanwinter. This might be the root cause. I can't reproduce it though, which version of docker are you using, and do you have anything in your .wslconfig ?

ryanwinter · 2025-04-04T03:18:28Z

I just updated to v4.40.0, but had the same issue with v4.39.0.

My .wslconfig contains the following at the moment:

[wsl2]
networkingMode = mirrored
autoProxy=false
dnsTunneling=true
guiApplications=false

[experimental]
autoMemoryReclaim = gradual

[network]
generateResolvConf = false

Also I restarted a few times and now it managed to boot up when I had an Ubuntu shell open. Here was the same kernel output:

[2025-04-04T00:37:07.567326800Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.441120118Z][init                  ] VM init started
[2025-04-04T00:37:07.567428600Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.441313325Z][init                  ] error mounting devtmpfs to /dev: device or resource busy
[2025-04-04T00:37:07.599953100Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.474336413Z][init                  ] added cpuset to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:37:07.600638100Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.474417313Z][init                  ] added cpu to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:37:07.600638100Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.474730465Z][init                  ] added io to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:37:07.600638100Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.474775268Z][init                  ] added memory to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:37:07.600638100Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.474786195Z][init                  ] added hugetlb to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:37:07.600638100Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.474795743Z][init                  ] added pids to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:37:07.600638100Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.474803982Z][init                  ] added rdma to /sys/fs/cgroup/cgroup.subtree_control
[2025-04-04T00:37:07.643420700Z][com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu-24.04 -e cat /etc/wsl.conf
[2025-04-04T00:37:07.745230600Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.619277480Z][init.socketforward    ] listening on virtual address: debug-socketforwarder
[2025-04-04T00:37:07.745230600Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.619325978Z][init.socketforward    ] listening on virtual address: perf-socketforwarder
[2025-04-04T00:37:07.745230600Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.619333431Z][init.socketforward    ] listening on virtual address: control-socketforwarder
[2025-04-04T00:37:07.745230600Z][com.docker.backend.exe.socketforward] [2025-04-04T00:37:07.619464348Z][vpnkit-bridge] /run/guest-services/socketforwarder-receive-fds.sock: successfully connected after 673.685986ms
[2025-04-04T00:37:07.745735900Z][com.docker.backend.exe.socketforward] [2025-04-04T00:37:07.619944314Z][vpnkit-bridge] sent fds so blocking forever
[2025-04-04T00:37:07.814488300Z][com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu-24.04 -e cat /etc/wsl.conf
[2025-04-04T00:37:07.829854600Z][com.docker.backend.exe.WSLBootstrap] grep: /etc/securetty: No such file or directory
[2025-04-04T00:37:07.833072800Z][com.docker.backend.exe.WSLBootstrap] getty: cmdline has console=hvc0 but does not exist in /etc/securetty; will not be able to log in as root on this tty hvc0.
[2025-04-04T00:37:07.834660300Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.709016790Z][init.socketforward    ] listening on virtual address: control-init
[2025-04-04T00:37:07.834660300Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.709292927Z][init.gpio             ] no PL061 controller found
[2025-04-04T00:37:07.867451100Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.741755060Z][init.ipc              ] 68fd7f26-pause/unpause ->  
[2025-04-04T00:37:07.875405500Z][com.docker.backend.exe.ipc][W] (784261a2-20) 971bd5d2-desktop_extensions C<-S ConnectionClosed GET /forwards/list (10.0005481s): Get "http://ipc/forwards/list": context deadline exceeded
[2025-04-04T00:37:07.875405500Z][com.docker.backend.exe.extensions] Get "http://ipc/forwards/list": context deadline exceeded
[2025-04-04T00:37:07.875405500Z][com.docker.backend.exe.ipc] (784261a2-22) 971bd5d2-desktop_extensions C->S desktop_extensions GET /forwards/list
[2025-04-04T00:37:07.875938100Z][com.docker.backend.exe.ipc] (784261a2-22) f34c7dd5-BackendAPI S<-C 971bd5d2-desktop_extensions GET /forwards/list
[2025-04-04T00:37:07.958158900Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.833607581Z][init                  ] platform has no virtio-net NICs
[2025-04-04T00:37:07.987948200Z][com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu-24.04 -e /mnt/wsl/docker-desktop/docker-desktop-user-distro sync-context-store /mnt/c/Users/<USER>/.docker/contexts
[2025-04-04T00:37:08.000392600Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.874976843Z][init                  ] listening on TCP port 5555 for internal Docker Hub proxy
[2025-04-04T00:37:08.010456000Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:07.885486907Z][init                  ] listening on TCP port 3128 for internal HTTP proxy
[2025-04-04T00:37:08.108137700Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:08.545012064Z][init                  ] exporting BPF pseudocode
[2025-04-04T00:37:08.108137700Z][com.docker.backend.exe.WSLBootstrap] [2025-04-04T00:37:08.545129019Z][init                  ] #12774

ryanwinter · 2025-04-04T05:10:53Z

So investigating a little more.

If I shutdown WSL and Docker, the start restart Docker:

[com.docker.backend.exe.WSLBootstrap] [init ][E] FATAL: initializing TAP AF_VSOCK: opening tap interface: no such file or directory

If I shutdown WSL and Docker, then start Ubuntu, then start Docker:

[com.docker.backend.exe.WSLBootstrap] [init ][E] FATAL: running services: running pause/unpause: error opening cgroup proc file at /sys/fs/cgroup/freezer/docker/docker-desktop/cgroup.procs: open /sys/fs/cgroup/freezer/docker/docker-desktop/cgroup.procs: no such file or directory

Then if I leave things running for a while and then restart Docker Desktop, it all just seems to work.

christoh · 2025-04-04T12:53:33Z

I see the following error starting the VM:

[init                  ][E] FATAL: initializing TAP AF_VSOCK: opening tap interface: no such file or directory

The solution for this is easy. WSL 2.5.4 does not load tun/tap by default. To fix:

Start your default WSL distribution:
sudo modprobe tap
sudo modprobe tun
Verify that tun and tap are loaded: lsmod
(Re)start Docker Desktop

In general this should be fixed by Docker to ensure the modules are loaded.

ThePlenkov · 2025-04-04T15:15:13Z

Did downgrade help to anyone? i tried wsl --uninstall + wsl --update and now I have:

wsl --version
WSL version: 2.4.13.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5716
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.5039

but docker doesn't start in wsl

rajshrimohanks · 2025-04-04T15:39:18Z

@ThePlenkov

Did downgrade help to anyone? i tried wsl --uninstall + wsl --update and now I have:
wsl --version
WSL version: 2.4.13.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5716
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.5039
but docker doesn't start in wsl

Downgrade helped me. I pretty much did

wsl --uninstall
wsl --install --no-distribution

and got everything working again.

C:\Users\rajshrimohanks>wsl --version
WSL version: 2.4.13.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5716
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26120.365

ThePlenkov · 2025-04-04T15:41:24Z

What is your docker version?

rajshrimohanks · 2025-04-04T15:53:44Z

What is your docker version?

@ThePlenkov

Docker Desktop v4.40.0

$ docker version
Client:
 Version:           28.0.4
 API version:       1.48
 Go version:        go1.23.7
 Git commit:        b8034c0
 Built:             Tue Mar 25 15:06:08 2025
 OS/Arch:           linux/amd64
 Context:           default

Server: Docker Desktop 4.0.0 ()
 Engine:
  Version:          28.0.4
  API version:      1.48 (minimum version 1.24)
  Go version:       go1.23.7
  Git commit:       6430e49
  Built:            Tue Mar 25 15:07:22 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.26
  GitCommit:        753481ec61c7c8955a23d6ff7bc8e4daed455734
 runc:
  Version:          1.2.5
  GitCommit:        v1.2.5-0-g59923ef
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

ryanwinter · 2025-04-04T17:07:38Z

I see the following error starting the VM:
[init                  ][E] FATAL: initializing TAP AF_VSOCK: opening tap interface: no such file or directory
The solution for this easy. WSL 2.5.4 does not load tun/tap by default. To fix:

Start your default WSL distribution:

sudo modprobe tap

sudo modprobe tun

Verify that tun and tap are loaded: lsmod

(Re)start Docker Desktop

In general this should be fixed by Docker to ensure the modules are loaded.

This would explain why launching the default distro fixes the issue, because it seems that the tun modules is loaded then.

OneBlue · 2025-04-04T19:22:58Z

I see the following error starting the VM:
[init                  ][E] FATAL: initializing TAP AF_VSOCK: opening tap interface: no such file or directory
The solution for this easy. WSL 2.5.4 does not load tun/tap by default. To fix:

Start your default WSL distribution:

sudo modprobe tap

sudo modprobe tun

Verify that tun and tap are loaded: lsmod

(Re)start Docker Desktop

In general this should be fixed by Docker to ensure the modules are loaded.

Thanks a lot, that's indeed something that we changed in 2.5.4. We'll revert this change in the next pre-release.

whoami730 · 2025-04-05T10:46:51Z

Thanks a lot, that's indeed something that we changed in 2.5.4. We'll revert this change in the next pre-release.

When will the next pre-release be available? Thanks.

voonyee · 2025-04-09T02:22:25Z

I see that the 2.5.6 pre-release is now available, see here: https://github.com/microsoft/WSL/releases/tag/2.5.6

ryanwinter · 2025-04-21T18:25:40Z

Everything is looking good for me in 2.5.6!

github-actions bot added the needs-author-feedback label Mar 27, 2025

microsoft-github-policy-service bot removed the needs-author-feedback label Mar 29, 2025

microsoft-github-policy-service bot added the needs-author-feedback label Apr 1, 2025

OneBlue added bug fixinbound and removed needs-author-feedback labels Apr 4, 2025

benhillis closed this as completed Apr 4, 2025

ThePlenkov mentioned this issue Apr 7, 2025

Endless "Docker desktop stopping" docker/for-win#12576

Open

3 tasks

jetvp mentioned this issue Apr 7, 2025

The rancher-desktop cannot start with WSL 2.5.4 (Pre-release) rancher-sandbox/rancher-desktop#8455

Closed

sundhaug92 mentioned this issue Apr 23, 2025

Docker WSL startup failed docker/for-win#14650

Open

WSL 2.5.4 Breaks Docker Desktop for Windows - Will not start #12748

WSL 2.5.4 Breaks Docker Desktop for Windows - Will not start #12748

Comments

FlattusBlastus commented Mar 27, 2025

Windows Version

WSL Version

Are you using WSL 1 or WSL 2?

Kernel Version

Distro Version

Other Software

Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs

github-actions bot commented Mar 27, 2025

Logs are required for review from WSL team

Uh oh!

aepot commented Mar 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

justknife commented Mar 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Tristan-MyAnaPro commented Mar 27, 2025

Uh oh!

justknife commented Mar 27, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

alexey-us commented Mar 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

auriz24 commented Mar 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Tristan-MyAnaPro commented Mar 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

alexey-us commented Mar 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

FlattusBlastus commented Mar 29, 2025

Uh oh!

craigktreasure commented Mar 31, 2025

Uh oh!

OneBlue commented Apr 1, 2025

Uh oh!

ryanwinter commented Apr 4, 2025

Uh oh!

ryanwinter commented Apr 4, 2025

Uh oh!

OneBlue commented Apr 4, 2025

Uh oh!

ryanwinter commented Apr 4, 2025

Uh oh!

ryanwinter commented Apr 4, 2025

Uh oh!

christoh commented Apr 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ThePlenkov commented Apr 4, 2025

Uh oh!

rajshrimohanks commented Apr 4, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ThePlenkov commented Apr 4, 2025

Uh oh!

rajshrimohanks commented Apr 4, 2025

Uh oh!

ryanwinter commented Apr 4, 2025

Uh oh!

OneBlue commented Apr 4, 2025

Uh oh!

whoami730 commented Apr 5, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

voonyee commented Apr 9, 2025

Uh oh!

ryanwinter commented Apr 21, 2025

Uh oh!

aepot commented Mar 27, 2025 •

edited

Loading

justknife commented Mar 27, 2025 •

edited

Loading

justknife commented Mar 27, 2025 •

edited

Loading

alexey-us commented Mar 28, 2025 •

edited

Loading

auriz24 commented Mar 28, 2025 •

edited

Loading

Tristan-MyAnaPro commented Mar 28, 2025 •

edited

Loading

alexey-us commented Mar 28, 2025 •

edited

Loading

christoh commented Apr 4, 2025 •

edited

Loading

rajshrimohanks commented Apr 4, 2025 •

edited

Loading

whoami730 commented Apr 5, 2025 •

edited

Loading