Docker stopped working in WSL 2.3.11.0

[neoGeneva]

Windows Version

Microsoft Windows [Version 10.0.22635.3930]

WSL Version

2.3.11.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

6.6.36.3-microsoft-standard-WSL2

Distro Version

Ubuntu 20.04

Other Software

Docker version 27.0.3, build 7d4bcd8

Repro Steps

1. Update WSL via windows store
2. Launch Docker

Expected Behavior

Docker to launch successfully

Actual Behavior

Docker fails to launch

Diagnostic Logs

No response

Some additional context

This morning WSL was updated via the Windows store, after that Docker failed to launch with a generic "exit code 1" error message. I uninstalled and reinstalled Docker and then it still failed to launch complaining it couldn't get the disk size.

I've seen some other issues related to Docker #11742 and #11771 and kernel version 6.6.36.3, but those don't seem to apply to me since I'm not building the kernel my self (installing from Microsoft Store), and I don't have "kernel=" in my .wslconfig.

Also, installing Docker using Hyper-V instead of WSL has no problems.

[github-actions]

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 scipt will output the path of the log file once done.

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 wsl-gh-logs@microsoft.com 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'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

• After latest Windows update I can't run WSL version 2 and Docker is not launching on Windows 10 Enterprise for Virtual Desktop (#7332), similarity score: 0.75
• Docker ceased working after upgrading to custom kernel version 6.6.36.3 (#11771), similarity score: 0.74
• WSL2 + DockerDesktop doesn't work - Remote procedure call failed. (#6041), similarity score: 0.73
• WSL2 2.0.1.0 Cannot start. (#10545), similarity score: 0.73
• 2.0.1.0 Unable to start wsl, unable to upgrade wsl, unable to downgrade wsl (#10582), similarity score: 0.72

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[wmmc88]

I ran into the same issue. Rolling back WSL to 2.2.4 via the installer at https://github.com/microsoft/WSL/releases/tag/2.2.4 mitigated this issue for me for now.

It seems like WU updated me to the 2.3.11 prerelease.

[elsaco]

@neoGeneva docker inside WSL is not working anymore? It might have to do with modules loading. On an non-systemd I can't load any WSL modules. On a systemd enabled WSL distro modules load fine, and docker engine works also:

ubuntu@eleven:~$ wslinfo --wsl-version
2.3.11
ubuntu@eleven:~$ docker info
Client: Docker Engine - Community
 Version:    26.1.4
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.14.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.27.1
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 26.1.4
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: cgroupfs
 Cgroup Version: 1
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: d2d58213f83a351ca8f528a95fbd145f5654e957
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  seccomp
   Profile: builtin
 Kernel Version: 6.6.36.3-microsoft-standard-WSL2
 Operating System: Ubuntu 24.04 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 7.757GiB
 Name: eleven
 ID: 49698596-f698-4988-846b-b652beca4bd4
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

[dbalabka]

Thanks, @wmmc88. Rollback was the only option for me, and it works https://github.com/microsoft/WSL/releases/tag/2.2.4

[elsaco]

On Windows side docker engine wouldn't start after wsl upgrade to 2.3.11, but it works after a docker upgrade:

Before:

and after docker upgrade:

[AnthonyMastrean]

I'm having trouble starting multiple recent versions of Docker Desktop. I can't get the notification panel to open at all, but it's showing multiple red notification counts. Most recently, I was able to capture this:

Unable to calculate image disk size

I'm seeing multiple events from WSL in the event log/viewer:

The description for Event ID 0 from source WSL cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Failed to create network endpoint with address: '172.28.92.131', assigned new address: '172.24.38.138'

The message resource is present but the message was not found in the message table

If downgrading to WSL 2.2.4 is a temporary solution, is there any way to prevent the Microsoft Store from upgrading it again?

[zcobol]

[com.docker.backend.exe.wslintegration] exited the watch loop of wsl distro agents
[com.docker.backend.exe.wslintegration] updating integration, default distro: true, additional distros: [], kubernetes enabled: false, kubernetes listener active: false, mustMergeKubeconfig: false
[com.docker.backend.exe.wslintegration] starting distro watcher
[com.docker.backend.exe.wslintegration] current active agents before sync: 0
[com.docker.backend.exe.wslintegration] active agents: 0
[com.docker.backend.exe.wslintegration] adding a wsl agent for new distro Ubuntu
[com.docker.backend.exe.ipc] 1ff0b792-wslintegrationagent-Ubuntu -> \\.\pipe\dockerWSLCrossDistroService CrossDistroService
[com.docker.backend.exe.wslintegration] done syncing agents
[com.docker.backend.exe.wsldistroproxy] start wsl integration for distro Ubuntu
[com.docker.backend.exe.wsldistroproxy] Configuring docker credstore to use desktop.exe
[com.docker.backend.exe.wsldistroproxy] credsStore already set to desktop.exe
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e whoami
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -u root -e sh -c ( addgroup docker || true ) && addgroup "root" docker
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -u root -e sh -c ( groupadd docker || true ) && usermod -aG docker "root"
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e cat /etc/wsl.conf
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e cat /etc/wsl.conf
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e /mnt/wsl/docker-desktop/docker-desktop-user-distro sync-context-store /mnt/c/Users/zcobol/.docker/contexts
[com.docker.backend.exe.wsldistroproxy][W] syncing context store in Ubuntu distro: cli contexts not resynced: exit status 1
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e cat /etc/wsl.conf
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e cat /etc/wsl.conf
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e /mnt/wsl/docker-desktop/docker-desktop-user-distro sync-home-subdir /mnt/c/Users/zcobol/.aws
[com.docker.backend.exe.wsldistroproxy][W] syncing ~/.aws in Ubuntu distro: path .aws not synced: exit status 1
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e cat /etc/wsl.conf
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e cat /etc/wsl.conf
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e /mnt/wsl/docker-desktop/docker-desktop-user-distro sync-home-subdir /mnt/c/Users/zcobol/.azure
[com.docker.backend.exe.wsldistroproxy][W] syncing ~/.azure in Ubuntu distro: path .azure not synced: exit status 1
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e cat /etc/wsl.conf
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e cat /etc/wsl.conf
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e /mnt/wsl/docker-desktop/docker-desktop-user-distro sync-file /mnt/c/Users/zcobol/.docker/features.json ~/.docker/features.json
[com.docker.backend.exe.wsldistroproxy][W] syncing ~/.docker/features.json in Ubuntu distro: syncing windows path /mnt/c/Users/zcobol/.docker/features.json to ~/.docker/features.json: exit status 1
[com.docker.backend.exe.wsldistroproxy] Killing CLI API server running at /root/.docker/run/docker-cli-api.sock
[com.docker.backend.exe.wsldistroproxy] Starting WSL Distro proxy
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -e cat /etc/wsl.conf
[com.docker.backend.exe.wsldistroproxy] wsl.exe -d Ubuntu -u root -e /mnt/wsl/docker-desktop/docker-desktop-user-distro proxy --distro-name Ubuntu --docker-desktop-root /mnt/wsl/docker-desktop C:\Program Files\Docker\Docker\resources
[com.docker.backend.exe.wslintegration] distro agent Ubuntu exited unexpectedly: running wsl distro proxy in Ubuntu distro: exit status 1
[com.docker.backend.exe.wslintegration] attempting recovery from agent Ubuntu error: running wsl distro proxy in Ubuntu distro: exit status 1
[com.docker.backend.exe.report] reporting error to user: running wsl distro proxy in Ubuntu distro: exit status 1

[neoGeneva]

Enabling systemd within WSL as described here resolved the issue for me. docker/for-win#14198 (comment)

[andy-sixtystores]

For me the issue was related to WSL 2.3.11 Pre-release.
Check your version with wsl --version.

I downloaded the installer for 2.4.4 (Latest) restarted the computer and docker loaded as normal.
Download WSL from the official release page - https://github.com/microsoft/WSL/releases

[JonathanPitre]

To revert back on 2.2.4.0 run the following from a Terminal with admin rights

wsl --shutdown
wsl --uninstall
wsl --update
wsl --version (ensure you see 2.2.4.0)