Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Docker desktop stuck at starting after install #13351

Open
3 tasks done
mkhoatd opened this issue Apr 1, 2023 · 4 comments
Open
3 tasks done

Docker desktop stuck at starting after install #13351

mkhoatd opened this issue Apr 1, 2023 · 4 comments

Comments

@mkhoatd
Copy link

mkhoatd commented Apr 1, 2023

  • I have tried with the latest version of Docker Desktop
  • I have tried disabling enabled experimental features
  • I have uploaded Diagnostics
  • Diagnostics ID: 360DF609-3C44-4CC0-A7BC-14D342917C64/20230401152433

Actual behavior

Docker desktop stuck at starting after install

Expected behavior

Run normally

Information

  • Windows Version: 22621.1413
  • Docker Desktop Version: 4.17.0
  • WSL2 or Hyper-V backend? WSL2
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

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?
[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? [ 849.892282] EXT4-fs error (device sdc): ext4_put_super:1188: comm wsl-bootstrap: Couldn't clean up the journal
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-01T15:31:39.009503100Z][com.docker.diagnose.exe][I] ipc.NewClient: 6ea83670-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI
[2023-04-01T15:31:39.010008200Z][com.docker.diagnose.exe][I] (f39f0c01) 6ea83670-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-04-01T15:31:39.010537600Z][com.docker.diagnose.exe][W] (f39f0c01) 6ea83670-com.docker.diagnose C<-S NoResponse GET /docker (0s): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-01T15:31:39.010537600Z][com.docker.diagnose.exe][I] (f39f0c01-1) 6ea83670-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-01T15:31:39.011064900Z][com.docker.diagnose.exe][W] (f39f0c01-1) 6ea83670-com.docker.diagnose C<-S NoResponse GET /ping (527.3µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-01T15:31:40.017329200Z][com.docker.diagnose.exe][I] (f39f0c01-2) 6ea83670-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-01T15:31:40.017834000Z][com.docker.diagnose.exe][W] (f39f0c01-2) 6ea83670-com.docker.diagnose C<-S NoResponse GET /ping (504.8µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-01T15:31:41.027916000Z][com.docker.diagnose.exe][I] (f39f0c01-3) 6ea83670-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-01T15:31:41.028565300Z][com.docker.diagnose.exe][W] (f39f0c01-3) 6ea83670-com.docker.diagnose C<-S NoResponse GET /ping (649.3µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-01T15:31:42.030514300Z][com.docker.diagnose.exe][I] (f39f0c01-4) 6ea83670-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-01T15:31:42.030514300Z][com.docker.diagnose.exe][W] (f39f0c01-4) 6ea83670-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-01T15:31:43.042578500Z][com.docker.diagnose.exe][I] (f39f0c01-5) 6ea83670-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-01T15:31:43.042578500Z][com.docker.diagnose.exe][W] (f39f0c01-5) 6ea83670-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-01T15:31:44.055061100Z][com.docker.diagnose.exe][I] (f39f0c01-6) 6ea83670-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-01T15:31:44.055061100Z][com.docker.diagnose.exe][W] (f39f0c01-6) 6ea83670-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-01T15:31:45.067801000Z][com.docker.diagnose.exe][I] (f39f0c01-7) 6ea83670-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-01T15:31:45.067866900Z][com.docker.diagnose.exe][W] (f39f0c01-7) 6ea83670-com.docker.diagnose C<-S NoResponse GET /ping (65.9µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-01T15:31:46.082736300Z][com.docker.diagnose.exe][I] (f39f0c01-8) 6ea83670-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-01T15:31:46.082736300Z][com.docker.diagnose.exe][W] (f39f0c01-8) 6ea83670-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: 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_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?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[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? [ 849.892282] EXT4-fs error (device sdc): ext4_put_super:1188: comm wsl-bootstrap: Couldn't clean up the journal
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0011: are the LinuxKit services running?
[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: 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_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: 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_linux/v1.24/networks": open //./pipe/docker_engine_linux: The system cannot find the file specified.

Please note the following 4 warnings:

1 : The check: is the WSL 2 Linux filesystem corrupt?
Produced the following warning: [ 849.892282] EXT4-fs error (device sdc): ext4_put_super:1188: comm wsl-bootstrap: Couldn't clean up the journal

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:
microsoft/WSL#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.

2 : The check: is the Docker engine running?
Produced the following warning: Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

3 : The check: does the Docker API work?
Produced the following warning: 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_linux/v1.24/containers/json?limit=0": open //./pipe/docker_engine_linux: The system cannot find the file specified.

If the Docker API is not available from the host then Docker Desktop will not work correctly.

4 : The check: do Docker networks overlap with host IPs?
Produced the following warning: 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_linux/v1.24/networks": open //./pipe/docker_engine_linux: The system cannot find the file specified.

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address

Please investigate the following 1 issue:

1 : The test: is the WSL 2 Linux filesystem corrupt?
Failed with: [ 849.892282] EXT4-fs error (device sdc): ext4_put_super:1188: comm wsl-bootstrap: Couldn't clean up the journal

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:
microsoft/WSL#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.

Steps to reproduce the behavior

  1. Install docker desktop
  2. Start docker desktop
@chrisfleming
Copy link

I have exactly the same issue.

lsb_release -r
Release: 20.04
cat /proc/version
Linux version 5.15.90.1-microsoft-standard-WSL2 (oe-user@oe-host) (x86_64-msft-linux-gcc (GCC) 9.3.0, GNU ld (GNU Binutils) 2.34.0.20200220) #1 SMP Fri Jan 27 02:56:13 UTC 2023

dmesg | grep ext4
[ 154.692346] EXT4-fs error (device sdc): ext4_put_super:1188: comm weston: Couldn't clean up the journal

C:\Users\Chris_Fleming>"C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
[2023-04-05T10:49:02.743359700Z][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?

@chadjefferies
Copy link

Also having this issue. I tried re-installing Docker and re-enabling WSL.

[2023-04-06T23:32:34.519349200Z][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?
[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? [  519.556307] EXT4-fs error (device sdd): ext4_put_super:1188: comm wsl-bootstrap: Couldn't clean up the journal
[FAIL] DD0035: is the VM time synchronized? parsing time output: 2023-04-06T23:32:37+00:00: parsing time "2023-04-06T23:32:37+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"
[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-04-06T23:32:37.558719500Z][com.docker.diagnose.exe][I] ipc.NewClient: af1763c7-diagnose -> \\.\pipe\dockerDiagnosticd diagnosticsd
[2023-04-06T23:32:37.559230400Z][com.docker.diagnose.exe][I] (3cfc9d15) af1763c7-diagnose C->S diagnosticsd GET /ping
[2023-04-06T23:32:37.559230400Z][com.docker.diagnose.exe][W] (3cfc9d15) af1763c7-diagnose C<-S NoResponse GET /ping (0s): 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-04-06T23:32:37.559746600Z][com.docker.diagnose.exe][I] ipc.NewClient: 4417dad3-com.docker.diagnose -> \\.\pipe\dockerLifecycleServer VMDockerdAPI
[2023-04-06T23:32:37.559746600Z][com.docker.diagnose.exe][I] (adb07437) 4417dad3-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-04-06T23:32:37.560346300Z][com.docker.diagnose.exe][W] (adb07437) 4417dad3-com.docker.diagnose C<-S NoResponse GET /docker (599.7µs): Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-06T23:32:37.560849500Z][com.docker.diagnose.exe][I] (adb07437-1) 4417dad3-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-06T23:32:37.560849500Z][com.docker.diagnose.exe][W] (adb07437-1) 4417dad3-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-06T23:32:38.569228800Z][com.docker.diagnose.exe][I] (adb07437-2) 4417dad3-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-06T23:32:38.569228800Z][com.docker.diagnose.exe][W] (adb07437-2) 4417dad3-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-06T23:32:39.582455700Z][com.docker.diagnose.exe][I] (adb07437-3) 4417dad3-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-06T23:32:39.582455700Z][com.docker.diagnose.exe][W] (adb07437-3) 4417dad3-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-06T23:32:40.597010800Z][com.docker.diagnose.exe][I] (adb07437-4) 4417dad3-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-06T23:32:40.597010800Z][com.docker.diagnose.exe][W] (adb07437-4) 4417dad3-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-06T23:32:41.607341000Z][com.docker.diagnose.exe][I] (adb07437-5) 4417dad3-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-06T23:32:41.607341000Z][com.docker.diagnose.exe][W] (adb07437-5) 4417dad3-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-06T23:32:42.620934500Z][com.docker.diagnose.exe][I] (adb07437-6) 4417dad3-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-06T23:32:42.621448800Z][com.docker.diagnose.exe][W] (adb07437-6) 4417dad3-com.docker.diagnose C<-S NoResponse GET /ping (514.3µs): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-06T23:32:43.632141700Z][com.docker.diagnose.exe][I] (adb07437-7) 4417dad3-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-06T23:32:43.632141700Z][com.docker.diagnose.exe][W] (adb07437-7) 4417dad3-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-06T23:32:44.636163000Z][com.docker.diagnose.exe][I] (adb07437-8) 4417dad3-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-06T23:32:44.637210900Z][com.docker.diagnose.exe][W] (adb07437-8) 4417dad3-com.docker.diagnose C<-S NoResponse GET /ping (514.2µs): 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: 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_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?
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.
[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.
[2023-04-06T23:32:45.394950900Z][com.docker.diagnose.exe][I] ipc.NewClient: 52cae038-diagnose -> \\.\pipe\dockerDesktopLinuxEngine Proxy
[2023-04-06T23:32:45.394950900Z][com.docker.diagnose.exe][I] (92b8090e) 52cae038-diagnose C->S Proxy GET /desktop-diagnostics/ping
[2023-04-06T23:32:45.395492000Z][com.docker.diagnose.exe][W] (92b8090e) 52cae038-diagnose C<-S NoResponse GET /desktop-diagnostics/ping (541.1µs): Get "http://ipc/desktop-diagnostics/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-06T23:32:45.395492000Z][com.docker.diagnose.exe][I] (92b8090e-1) 52cae038-diagnose C->S Proxy GET /ping
[2023-04-06T23:32:45.395492000Z][com.docker.diagnose.exe][W] (92b8090e-1) 52cae038-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-06T23:32:46.403217600Z][com.docker.diagnose.exe][I] (92b8090e-2) 52cae038-diagnose C->S Proxy GET /ping
[2023-04-06T23:32:46.404328200Z][com.docker.diagnose.exe][W] (92b8090e-2) 52cae038-diagnose C<-S NoResponse GET /ping (1.1106ms): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-06T23:32:47.409106800Z][com.docker.diagnose.exe][I] (92b8090e-3) 52cae038-diagnose C->S Proxy GET /ping
[2023-04-06T23:32:47.409106800Z][com.docker.diagnose.exe][W] (92b8090e-3) 52cae038-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-06T23:32:48.423813300Z][com.docker.diagnose.exe][I] (92b8090e-4) 52cae038-diagnose C->S Proxy GET /ping
[2023-04-06T23:32:48.423813300Z][com.docker.diagnose.exe][W] (92b8090e-4) 52cae038-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-06T23:32:49.429394100Z][com.docker.diagnose.exe][I] (92b8090e-5) 52cae038-diagnose C->S Proxy GET /ping
[2023-04-06T23:32:49.429905900Z][com.docker.diagnose.exe][W] (92b8090e-5) 52cae038-diagnose C<-S NoResponse GET /ping (511.8µs): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-06T23:32:50.436318300Z][com.docker.diagnose.exe][I] (92b8090e-6) 52cae038-diagnose C->S Proxy GET /ping
[2023-04-06T23:32:50.436830800Z][com.docker.diagnose.exe][W] (92b8090e-6) 52cae038-diagnose C<-S NoResponse GET /ping (512.5µs): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-06T23:32:51.443233700Z][com.docker.diagnose.exe][I] (92b8090e-7) 52cae038-diagnose C->S Proxy GET /ping
[2023-04-06T23:32:51.443749500Z][com.docker.diagnose.exe][W] (92b8090e-7) 52cae038-diagnose C<-S NoResponse GET /ping (515.8µs): Get "http://ipc/ping": open \\.\pipe\dockerDesktopLinuxEngine: The system cannot find the file specified.
[2023-04-06T23:32:52.456989600Z][com.docker.diagnose.exe][I] (92b8090e-8) 52cae038-diagnose C->S Proxy GET /ping
[2023-04-06T23:32:52.457501600Z][com.docker.diagnose.exe][W] (92b8090e-8) 52cae038-diagnose C<-S NoResponse GET /ping (512µs): Get "http://ipc/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?
[PASS] DD0033: does the host have Internet access?
[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? [  519.556307] EXT4-fs error (device sdd): ext4_put_super:1188: comm wsl-bootstrap: Couldn't clean up the journal
[WARN] DD0035: is the VM time synchronized? parsing time output: 2023-04-06T23:32:37+00:00: parsing time "2023-04-06T23:32:37+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"
[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: 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_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: 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_linux/v1.24/networks": open //./pipe/docker_engine_linux: The system cannot find the file specified.

Please note the following 6 warnings:

1 : The check: is the WSL 2 Linux filesystem corrupt?
    Produced the following warning: [  519.556307] EXT4-fs error (device sdd): ext4_put_super:1188: comm wsl-bootstrap: Couldn't clean up the journal

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.


2 : The check: is the VM time synchronized?
    Produced the following warning: parsing time output: 2023-04-06T23:32:37+00:00: parsing time "2023-04-06T23:32:37+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"

The VM time must be in sync with the host, otherwise Docker Desktop will not work correctly.

Ensure you are using a modern WSL 2 kernel (see "wsl --update"). If this problem persists,
try manually synchronizing the VM clock with "sudo hwclock -s".

3 : The check: are the LinuxKit services running?
    Produced the following warning: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \\.\pipe\dockerDiagnosticd: The system cannot find the file specified.

The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.

4 : The check: is the Docker engine running?
    Produced the following warning: Get "http://ipc/docker": open \\.\pipe\dockerLifecycleServer: The system cannot find the file specified.

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

5 : The check: does the Docker API work?
    Produced the following warning: 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_linux/v1.24/containers/json?limit=0": open //./pipe/docker_engine_linux: The system cannot find the file specified.

If the Docker API is not available from the host then Docker Desktop will not work correctly.

6 : The check: do Docker networks overlap with host IPs?
    Produced the following warning: 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_linux/v1.24/networks": open //./pipe/docker_engine_linux: The system cannot find the file specified.

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address


Please investigate the following 2 issues:

1 : The test: is the WSL 2 Linux filesystem corrupt?
    Failed with: [  519.556307] EXT4-fs error (device sdd): ext4_put_super:1188: comm wsl-bootstrap: Couldn't clean up the journal

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.


2 : The test: is the VM time synchronized?
    Failed with: parsing time output: 2023-04-06T23:32:37+00:00: parsing time "2023-04-06T23:32:37+00:00" as "2006-01-02T15:04:05UTC": cannot parse "+00:00" as "UTC"

The VM time must be in sync with the host, otherwise Docker Desktop will not work correctly.

Ensure you are using a modern WSL 2 kernel (see "wsl --update"). If this problem persists,
try manually synchronizing the VM clock with "sudo hwclock -s".

@barnjamin barnjamin mentioned this issue Apr 12, 2023
Closed
@EoinLynch2
Copy link

Also having a similar issue.

Reinstalled docker multiple times.
Disabled and reenabled WSL2 and Hyper V multiple times.
Restarted services multiple times.
Restarted laptop multiple times.

[PASS] DD0027: is there available disk space on the host?
[FAIL] DD0028: is there available VM disk space? failed to retrieve the size information from ''
[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?
[FAIL] DD0024: is WSL installed? exit status 1
[FAIL] DD0025: are WSL distros installed? exit status 1
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? context deadline exceeded
[FAIL] DD0035: is the VM time synchronized? exit status 1
[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-04-18T23:01:20.374991100Z][com.docker.diagnose.exe][I] ipc.NewClient: 982d3263-diagnose -> \.\pipe\dockerDiagnosticd diagnosticsd
[2023-04-18T23:01:20.374991100Z][com.docker.diagnose.exe][I] (953e4cbb) 982d3263-diagnose C->S diagnosticsd GET /ping
[2023-04-18T23:01:20.375541700Z][com.docker.diagnose.exe][W] (953e4cbb) 982d3263-diagnose C<-S NoResponse GET /ping (550.6µ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-04-18T23:01:20.376100500Z][com.docker.diagnose.exe][I] ipc.NewClient: 30b537be-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI
[2023-04-18T23:01:20.376647600Z][com.docker.diagnose.exe][I] (7f9f7c53) 30b537be-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-04-18T23:01:20.376647600Z][com.docker.diagnose.exe][W] (7f9f7c53) 30b537be-com.docker.diagnose C<-S NoResponse GET /docker (0s): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-18T23:01:20.376647600Z][com.docker.diagnose.exe][I] (7f9f7c53-1) 30b537be-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-18T23:01:20.377195600Z][com.docker.diagnose.exe][W] (7f9f7c53-1) 30b537be-com.docker.diagnose C<-S NoResponse GET /ping (548µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.[2023-04-18T23:01:21.384902500Z][com.docker.diagnose.exe][I] (7f9f7c53-2) 30b537be-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-18T23:01:21.384902500Z][com.docker.diagnose.exe][W] (7f9f7c53-2) 30b537be-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-18T23:01:22.392134600Z][com.docker.diagnose.exe][I] (7f9f7c53-3) 30b537be-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-18T23:01:22.394156100Z][com.docker.diagnose.exe][W] (7f9f7c53-3) 30b537be-com.docker.diagnose C<-S NoResponse GET /ping (1.025ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-18T23:01:23.405258200Z][com.docker.diagnose.exe][I] (7f9f7c53-4) 30b537be-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-18T23:01:23.406791500Z][com.docker.diagnose.exe][W] (7f9f7c53-4) 30b537be-com.docker.diagnose C<-S NoResponse GET /ping (1.5333ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-18T23:01:24.420580100Z][com.docker.diagnose.exe][I] (7f9f7c53-5) 30b537be-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-18T23:01:24.422082900Z][com.docker.diagnose.exe][W] (7f9f7c53-5) 30b537be-com.docker.diagnose C<-S NoResponse GET /ping (1.5028ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-18T23:01:25.432932500Z][com.docker.diagnose.exe][I] (7f9f7c53-6) 30b537be-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-18T23:01:25.434796700Z][com.docker.diagnose.exe][W] (7f9f7c53-6) 30b537be-com.docker.diagnose C<-S NoResponse GET /ping (1.8642ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-18T23:01:26.437602500Z][com.docker.diagnose.exe][I] (7f9f7c53-7) 30b537be-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-18T23:01:26.438452000Z][com.docker.diagnose.exe][W] (7f9f7c53-7) 30b537be-com.docker.diagnose C<-S NoResponse GET /ping (849.5µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-04-18T23:01:27.449880500Z][com.docker.diagnose.exe][I] (7f9f7c53-8) 30b537be-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-04-18T23:01:27.451445400Z][com.docker.diagnose.exe][W] (7f9f7c53-8) 30b537be-com.docker.diagnose C<-S NoResponse GET /ping (1.5649ms): 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.
[PASS] DD0013: is the $PATH ok?
error during connect: This error may indicate that the docker daemon is not running.: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.24/containers/json": open //./pipe/docker_engine: The system cannot find the file specified.
[FAIL] DD0003: is the Docker CLI working? exit status 1
[FAIL] DD0005: is the user in the docker-users group? The user name could not be found.
[PASS] DD0038: is the connection to Docker working?
2023/04/19 00:01:34 error checking if default wsl distro is running: exit status 1

@markuszeller
Copy link

markuszeller commented Aug 18, 2023 •
edited
Loading

Same for me

Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[SKIP] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[SKIP] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[SKIP] 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? [  615.918150] EXT4-fs error (device sdc): ext4_put_super:1188: comm wsl-bootstrap: Couldn't clean up the journal
[PASS] DD0035: is the VM time synchronized?
[FAIL] DD0017: can a VM be started? prereq failed: is the WSL 2 Linux filesystem corrupt?
[FAIL] DD0016: is the LinuxKit VM running? prereq failed: can a VM be started?
[FAIL] DD0011: are the LinuxKit services running? prereq failed: is the LinuxKit VM running?
[FAIL] DD0004: is the Docker engine running? prereq failed: are the LinuxKit services running?
[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? prereq failed: is the Docker engine running?
[PASS] DD0013: is the $PATH ok?
[FAIL] DD0003: is the Docker CLI working? prereq failed: is the Docker engine running?
[FAIL] DD0005: is the user in the docker-users group? prereq failed: is the LinuxKit VM running?
[FAIL] DD0038: is the connection to Docker working? prereq failed: is the Docker engine running?
[FAIL] DD0014: are the backend processes running? prereq failed: is the LinuxKit VM running?
[FAIL] DD0007: is the backend responding? prereq failed: are the backend processes running?
[PASS] DD0008: is the native API responding?
[FAIL] DD0009: is the vpnkit API responding? prereq failed: are the backend processes running?
[FAIL] DD0010: is the Docker API proxy responding? prereq failed: are the backend processes running?
[SKIP] DD0006: is the Docker Desktop Service responding?
[FAIL] DD0030: is the image access management authorized? prereq failed: is the Docker engine running?
[PASS] DD0033: does the host have Internet access?
[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? [  615.918150] EXT4-fs error (device sdc): ext4_put_super:1188: comm wsl-bootstrap: Couldn't clean up the journal
[PASS] DD0035: is the VM time synchronized?
[WARN] DD0017: can a VM be started? prereq failed: is the WSL 2 Linux filesystem corrupt?
[WARN] DD0016: is the LinuxKit VM running? prereq failed: can a VM be started?
[WARN] DD0011: are the LinuxKit services running? prereq failed: is the LinuxKit VM running?
[WARN] DD0004: is the Docker engine running? prereq failed: are the LinuxKit services running?
[PASS] DD0015: are the binary symlinks installed?
[WARN] DD0031: does the Docker API work? prereq failed: is the Docker engine running?
[WARN] DD0032: do Docker networks overlap with host IPs? prereq failed: does the Docker API work?

I also noticed it shows device sdc which does not exist. When I sudo fdisk -l I find sda, sdb, sdd, sde and sdf.

Update:
sdc belongs to my Ubuntu 22.04

I've removed Docker Desktop and downgraded to 4.21.1 which worked immediately!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@markuszeller @chrisfleming @chadjefferies @EoinLynch2 @mkhoatd