Win10 - A timeout occured while waiting for a WSL integration

Docker for Windows suddenly refuses to start for me, it says:

An unexpected error occurred
A timeout occured while waiting for a WSL integration agent to become ready.

This can occur when starting after an abrupt termination. To work around the issue, please terminate WSL (wsl --shutdown) and start Docker Desktop again. If the issue persists please collect diagnostics and submit an issue (Troubleshoot Docker Desktop | Docker Docs).

Error details:
1 error occurred:

  • starting WSL integration service: synchronising agents: starting added distros: 1 error occurred:
  • waiting for WSL integration for Ubuntu: waiting for WSL distro integration to become ready in “Ubuntu”: timeout

Content of self-diagnose.txt:

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? exit status 1
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json?limit=0": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[PASS] DD0013: is the $PATH ok?
[FAIL] DD0003: is the Docker CLI working? exit status 1
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0038: is the connection to Docker working?
[FAIL] DD0014: are the backend processes running? 2 errors occurred:
	* com.docker.proxy.exe is not running
	* com.docker.vpnkit.exe is not running


[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[FAIL] DD0009: is the vpnkit API responding? open \\.\pipe\dockerVpnKitDiagnostics: The system cannot find the file specified.
[FAIL] DD0010: is the Docker API proxy responding? failed to ping Docker proxy API with error: Get "http://ipc/desktop-diagnostics/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[PASS] DD0006: is the Docker Desktop Service responding?
[SKIP] DD0030: is the image access management authorized?
[WARN] DD0033: does the host have Internet access? unable to fetch http://docker.com/
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[WARN] DD0029: is the WSL 2 Linux filesystem corrupt? exit status 1
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[WARN] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[WARN] DD0004: is the Docker engine running? Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[PASS] DD0015: are the binary symlinks installed?
[WARN] DD0031: does the Docker API work? error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json?limit=0": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[WARN] DD0032: do Docker networks overlap with host IPs? error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/networks": open //./pipe/docker_engine_linux: The system cannot find the file specified.
1 failures detected
1 : is the WSL 2 Linux filesystem corrupt?
    Failed with: exit status 1
If the WSL 2 Linux filesystem is corrupt then Docker Desktop cannot start.
There is a known issue fixed in Windows Insider builds which can cause filesystem corruption, see:
https://github.com/microsoft/WSL/issues/5895 .

Try running "wsl --shutdown" to stop your WSL Virtual Machine. When it restarts it will
run a filesystem check and hopefully fix the problem.


self-diagnose took 51.2408263s

Log: https://put.icu/s/3htu5uba.txt
Take note that I can use my WSL2 Ubuntu 20.04 LTS distro just fine, it does not look corrupt.
I tried to reinstall Docker, it did not help. Also tried “apt-get upgrade” in the distro, also didn’t help. Rebooting PC doesn’t help.
OS: Windows 10 22H2 build 19045.2728 Windows Feature Experience Pack 120.2212.4190.0
App Version: 4.17.1 (101757)

I’m getting the same error message in Windows 11.

Things I have attempted so far:
*Stop the Docker service and restart by launching Docker Desktop
*Turn off Control Flow Guard
*Uninstall Docker Desktop 4.17.0
*Reinstall with version 4.17.1
*Shutdown WSL

After doing all that, I’m able to start Docker Desktop successfully, but when I launch an Ubuntu 20.04 terminal and run:

sudo docker ps -a

Docker Desktop crashes with the same error @vcsajen gets:

Error details:
1 error occurred:
* starting WSL integration service: synchronising agents: starting added distros: 1 error occurred:
* waiting for WSL integration for Ubuntu-20.04: waiting for WSL distro integration to become ready in “Ubuntu-20.04”: timeout

When I run the diagnose.exe check:

C:\Users\Owner\Downloads>"C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
[2023-03-22T21:10:58.372959000Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[FAIL] DD0001: is the application running? Docker is not running
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? exit status 1
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-03-22T21:11:27.418372900Z][com.docker.diagnose.exe][I] ipc.NewClient: a2627442-diagnose -> \\.\pipe\dockerDiagnosticd diagnosticsd
[2023-03-22T21:11:27.418372900Z][com.docker.diagnose.exe][I] (5fe949c0) a2627442-diagnose C->S diagnosticsd GET /ping
[2023-03-22T21:11:27.419029300Z][com.docker.diagnose.exe][W] (5fe949c0) a2627442-diagnose C<-S NoResponse GET /ping (656.4µs): Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.

[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-03-22T21:11:27.420585800Z][com.docker.diagnose.exe][I] ipc.NewClient: 87281ced-com.docker.diagnose -> \\.\pipe\dockerLifecycleServer VMDockerdAPI
[2023-03-22T21:11:27.420678200Z][com.docker.diagnose.exe][I] (53f30398) 87281ced-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-03-22T21:11:27.421279600Z][com.docker.diagnose.exe][W] (53f30398) 87281ced-com.docker.diagnose C<-S NoResponse GET /docker (601.4µs): Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-03-22T21:11:27.421279600Z][com.docker.diagnose.exe][I] (53f30398-1) 87281ced-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-03-22T21:11:27.421785400Z][com.docker.diagnose.exe][W] (53f30398-1) 87281ced-com.docker.diagnose C<-S NoResponse GET /ping (505.8µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-03-22T21:11:28.423127600Z][com.docker.diagnose.exe][I] (53f30398-2) 87281ced-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-03-22T21:11:28.423127600Z][com.docker.diagnose.exe][W] (53f30398-2) 87281ced-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-03-22T21:11:29.429333000Z][com.docker.diagnose.exe][I] (53f30398-3) 87281ced-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-03-22T21:11:29.429450700Z][com.docker.diagnose.exe][W] (53f30398-3) 87281ced-com.docker.diagnose C<-S NoResponse GET /ping (117.7µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-03-22T21:11:30.433882100Z][com.docker.diagnose.exe][I] (53f30398-4) 87281ced-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-03-22T21:11:30.434401200Z][com.docker.diagnose.exe][W] (53f30398-4) 87281ced-com.docker.diagnose C<-S NoResponse GET /ping (519.1µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-03-22T21:11:31.437255300Z][com.docker.diagnose.exe][I] (53f30398-5) 87281ced-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-03-22T21:11:31.437441800Z][com.docker.diagnose.exe][W] (53f30398-5) 87281ced-com.docker.diagnose C<-S NoResponse GET /ping (186.5µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-03-22T21:11:32.452030700Z][com.docker.diagnose.exe][I] (53f30398-6) 87281ced-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-03-22T21:11:32.452030700Z][com.docker.diagnose.exe][W] (53f30398-6) 87281ced-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-03-22T21:11:33.455979300Z][com.docker.diagnose.exe][I] (53f30398-7) 87281ced-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-03-22T21:11:33.455979300Z][com.docker.diagnose.exe][W] (53f30398-7) 87281ced-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-03-22T21:11:34.457652800Z][com.docker.diagnose.exe][I] (53f30398-8) 87281ced-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-03-22T21:11:34.457652800Z][com.docker.diagnose.exe][W] (53f30398-8) 87281ced-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.

[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json?limit=0": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[FAIL] DD0013: is the $PATH ok? unable to find docker executable on PATH
[FAIL] DD0003: is the Docker CLI working? exec: "docker": executable file not found in %PATH%
[PASS] DD0005: is the user in the docker-users group?
[FAIL] DD0038: is the connection to Docker working? HTTP GET https://login.docker.com: Get "https://login.docker.com": proxyconnect tcp: open \\.\pipe\dockerHTTPProxy: The system cannot find the file specified.
[FAIL] DD0014: are the backend processes running? 3 errors occurred:
        * com.docker.proxy.exe is not running
        * com.docker.backend.exe is not running
        * com.docker.vpnkit.exe is not running


[FAIL] DD0007: is the backend responding? failed to ping com.docker.backend with error: Get "http://ipc/ping": open \\.\pipe\dockerBackendApiServer: The system cannot find the file specified.
[2023-03-22T21:11:40.199626400Z][com.docker.diagnose.exe][I] ipc.NewClient: e9a8b6f6-diagnose -> \\.\pipe\dockerBackendApiServer BackendAPI

My WSL2 Ubuntu is working just fine also.

Finally, the output of the command wsl -l -v:

NAME                   STATE           VERSION
* Ubuntu-20.04           Stopped         2
  docker-desktop         Running         2
  docker-desktop-data    Running         2

Had the same problem and after pulling my hair for days i found a solution.

Navigate to Appdata/Roaming/Docker folder in your user account
Open the settings file(JSON file) and make sure the following are set this way :point_down:

"integratedWslDistros" : [ ]
"enableIntegrationWithDefaultWslDistro" : false,

Save the changes and restart docker desktop

Hope this helps :muscle::muscle:

9 Likes

how do i find this file my docker wont run in windows 11 latest updates

If “this” refers to

Then you can use %APPDATA%\Docker in the explorer to navigate to that folder.

1 Like

It also worked for me. I was struggling with it for couple days. Thank you for the tip!

Totally works. Thanks very much for the information

This solution worked for me too. Thank you for sharing!

Yes it worked for me. Thank you

It worked for me too. Thank you !