[x] I have tried with the latest version of Docker Desktop
[x] I have tried disabling enabled experimental features
[x] I have uploaded Diagnostics
Diagnostics ID:
Actual behavior
The installer/updater for Docker Desktop keeps installing the WSL system component
Expected behavior
The system component is deprecated and all WSL installations in the future will be from the Microsoft Store. Docker Desktop should detect if the Microsoft Store version is installed and then not try to install the system component.
Information
Windows Version:
Docker Desktop Version:
WSL2 or Hyper-V backend?
Are you running inside a virtualized Windows e.g. on a cloud server or a VM:
Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
Diagnostics output:
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[FAIL] DD0002: does the bootloader have virtualization enabled? contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:46:59.286830000Z][com.docker.diagnose.exe][I] ipc.NewClient: 247fb9e2-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service
[2023-05-15T18:46:59.286830000Z][com.docker.diagnose.exe][I] (859389ec) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /hyperv/bootloader
[2023-05-15T18:46:59.287419600Z][com.docker.diagnose.exe][W] (859389ec) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /hyperv/bootloader (589.6µs): Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:46:59.287925500Z][com.docker.diagnose.exe][I] (859389ec-1) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:46:59.287925500Z][com.docker.diagnose.exe][W] (859389ec-1) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:00.298116900Z][com.docker.diagnose.exe][I] (859389ec-2) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:00.298116900Z][com.docker.diagnose.exe][W] (859389ec-2) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:01.309133200Z][com.docker.diagnose.exe][I] (859389ec-3) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:01.309234900Z][com.docker.diagnose.exe][W] (859389ec-3) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (101.7µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:02.324701800Z][com.docker.diagnose.exe][I] (859389ec-4) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:02.325223900Z][com.docker.diagnose.exe][W] (859389ec-4) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:03.329428000Z][com.docker.diagnose.exe][I] (859389ec-5) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:03.329428000Z][com.docker.diagnose.exe][W] (859389ec-5) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:04.343544300Z][com.docker.diagnose.exe][I] (859389ec-6) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:04.343544300Z][com.docker.diagnose.exe][W] (859389ec-6) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:05.354218900Z][com.docker.diagnose.exe][I] (859389ec-7) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:05.354724100Z][com.docker.diagnose.exe][W] (859389ec-7) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (505.2µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:06.358133700Z][com.docker.diagnose.exe][I] (859389ec-8) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:06.358133700Z][com.docker.diagnose.exe][W] (859389ec-8) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[FAIL] DD0022: is the Virtual Machine Platform Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:06.375442700Z][com.docker.diagnose.exe][I] ipc.NewClient: e40388cf-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service
[2023-05-15T18:47:06.375962600Z][com.docker.diagnose.exe][I] (c5ebe26a) e40388cf-com.docker.diagnose C->S com.docker.service POST /windowsfeatures/check: [VirtualMachinePlatform (Virtual Machine Platform)]
[2023-05-15T18:47:06.376486200Z][com.docker.diagnose.exe][W] (c5ebe26a) e40388cf-com.docker.diagnose C<-S NoResponse POST /windowsfeatures/check (523.6µs): Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:06.376486200Z][com.docker.diagnose.exe][I] (c5ebe26a-1) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:06.377001000Z][com.docker.diagnose.exe][W] (c5ebe26a-1) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (514.8µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:07.386488400Z][com.docker.diagnose.exe][I] (c5ebe26a-2) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:07.386994800Z][com.docker.diagnose.exe][W] (c5ebe26a-2) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (506.4µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:08.400404200Z][com.docker.diagnose.exe][I] (c5ebe26a-3) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:08.400909200Z][com.docker.diagnose.exe][W] (c5ebe26a-3) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (505µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:09.413116500Z][com.docker.diagnose.exe][I] (c5ebe26a-4) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:09.413235000Z][com.docker.diagnose.exe][W] (c5ebe26a-4) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (118.5µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:10.425977500Z][com.docker.diagnose.exe][I] (c5ebe26a-5) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:10.426493100Z][com.docker.diagnose.exe][W] (c5ebe26a-5) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (515.6µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:11.434871300Z][com.docker.diagnose.exe][I] (c5ebe26a-6) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:11.434871300Z][com.docker.diagnose.exe][W] (c5ebe26a-6) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:12.435872400Z][com.docker.diagnose.exe][I] (c5ebe26a-7) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:12.435872400Z][com.docker.diagnose.exe][W] (c5ebe26a-7) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:13.443641600Z][com.docker.diagnose.exe][I] (c5ebe26a-8) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:13.443742600Z][com.docker.diagnose.exe][W] (c5ebe26a-8) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (101µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[FAIL] DD0021: is the WSL 2 Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:13.444305100Z][com.docker.diagnose.exe][I] ipc.NewClient: 32abf756-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service
[2023-05-15T18:47:13.444305100Z][com.docker.diagnose.exe][I] (22261ebe) 32abf756-com.docker.diagnose C->S com.docker.service POST /windowsfeatures/check: [Microsoft-Windows-Subsystem-Linux (Windows Subsystem for Linux)]
[2023-05-15T18:47:13.444305100Z][com.docker.diagnose.exe][W] (22261ebe) 32abf756-com.docker.diagnose C<-S NoResponse POST /windowsfeatures/check (0s): Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:13.444305100Z][com.docker.diagnose.exe][I] (22261ebe-1) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:13.445255500Z][com.docker.diagnose.exe][W] (22261ebe-1) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (950.4µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:14.459044200Z][com.docker.diagnose.exe][I] (22261ebe-2) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:14.459044200Z][com.docker.diagnose.exe][W] (22261ebe-2) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:15.468417700Z][com.docker.diagnose.exe][I] (22261ebe-3) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:15.468922200Z][com.docker.diagnose.exe][W] (22261ebe-3) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (504.5µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:16.469524000Z][com.docker.diagnose.exe][I] (22261ebe-4) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:16.469524000Z][com.docker.diagnose.exe][W] (22261ebe-4) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (108.2µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:17.471886600Z][com.docker.diagnose.exe][I] (22261ebe-5) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:17.471886600Z][com.docker.diagnose.exe][W] (22261ebe-5) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:18.484599600Z][com.docker.diagnose.exe][I] (22261ebe-6) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:18.484599600Z][com.docker.diagnose.exe][W] (22261ebe-6) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:19.495379700Z][com.docker.diagnose.exe][I] (22261ebe-7) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:19.495884900Z][com.docker.diagnose.exe][W] (22261ebe-7) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (505.2µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:20.497375400Z][com.docker.diagnose.exe][I] (22261ebe-8) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping
[2023-05-15T18:47:20.497375400Z][com.docker.diagnose.exe][W] (22261ebe-8) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[FAIL] DD0026: is the WSL LxssManager service running? LxssManager service is not running
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? [130374.746190] EXT4-fs error (device sdd): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal
[FAIL] DD0035: is the VM time synchronized? parsing time output: 2023-05-15T18:47:20+00:00: parsing time "2023-05-15T18:47:20+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?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0003: is the Docker CLI working?
[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?
[FAIL] DD0006: is the Docker Desktop Service responding? failed to ping com.docker.service with error: Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[2023-05-15T18:47:23.960639200Z][com.docker.diagnose.exe][I] ipc.NewClient: 7423d4d1-diagnose -> \\.\pipe\dockerBackendV2 Service
[2023-05-15T18:47:23.961172000Z][com.docker.diagnose.exe][I] (0c73eb00) 7423d4d1-diagnose C->S Service GET /ping
[2023-05-15T18:47:23.961172000Z][com.docker.diagnose.exe][W] (0c73eb00) 7423d4d1-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[WARN] DD0002: does the bootloader have virtualization enabled? contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[WARN] DD0022: is the Virtual Machine Platform Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[WARN] DD0021: is the WSL 2 Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[WARN] DD0026: is the WSL LxssManager service running? LxssManager service is not running
[WARN] DD0029: is the WSL 2 Linux filesystem corrupt? [130374.746190] EXT4-fs error (device sdd): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal
[WARN] DD0035: is the VM time synchronized? parsing time output: 2023-05-15T18:47:20+00:00: parsing time "2023-05-15T18:47:20+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?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0031: does the Docker API work?
[PASS] DD0032: do Docker networks overlap with host IPs?
Please note the following 25 warnings:
1 : The check: does the bootloader have virtualization enabled?
Produced the following warning: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled.
Run:
bcdedit /set hypervisorlaunchtype auto
2 : The check: does the bootloader have virtualization enabled?
Produced the following warning: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled.
Run:
bcdedit /set hypervisorlaunchtype auto
3 : The check: is the Virtual Machine Platform Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
4 : The check: is the WSL 2 Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
5 : The check: is the Virtual Machine Platform Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
6 : The check: is the WSL 2 Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
7 : The check: is the Virtual Machine Platform Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
8 : The check: is the WSL 2 Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
9 : The check: is the Virtual Machine Platform Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
10 : The check: is the WSL 2 Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
11 : The check: is the WSL LxssManager service running?
Produced the following warning: LxssManager service is not running
The WSL LxssManager service must be running. Try running `sc config LxssManager start=auto` from an Administrator cmd.exe.
12 : The check: is the Virtual Machine Platform Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
13 : The check: is the WSL 2 Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
14 : The check: is the Virtual Machine Platform Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
15 : The check: is the WSL 2 Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
16 : The check: is the WSL 2 Linux filesystem corrupt?
Produced the following warning: [130374.746190] EXT4-fs error (device sdd): ext4_put_super:1188: comm Xwayland: 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.
17 : The check: is the Virtual Machine Platform Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
18 : The check: is the WSL 2 Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
19 : The check: is the Virtual Machine Platform Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
20 : The check: is the WSL 2 Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
21 : The check: is the Virtual Machine Platform Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
22 : The check: is the WSL 2 Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
23 : The check: is the Virtual Machine Platform Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
24 : The check: is the WSL 2 Windows Feature enabled?
Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
25 : The check: is the VM time synchronized?
Produced the following warning: parsing time output: 2023-05-15T18:47:20+00:00: parsing time "2023-05-15T18:47:20+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".
Please investigate the following 3 issues:
1 : The test: does the bootloader have virtualization enabled?
Failed with: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled.
Run:
bcdedit /set hypervisorlaunchtype auto
2 : The test: is the Virtual Machine Platform Windows Feature enabled?
Failed with: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
3 : The test: is the Docker Desktop Service responding?
Failed with: failed to ping com.docker.service with error: Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Docker Desktop Service is needed to start the Docker engine. Open the list of Services and configure the Docker Desktop Service to start automatically.
Specifically this part is the problem:
2 : The test: is the Virtual Machine Platform Windows Feature enabled?
Failed with: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified.
The Virtual Machine Platform Windows Feature is needed to use WSL 2.
See https://docs.microsoft.com/en-us/windows/wsl/install-win10
Steps to reproduce the behavior
Uninstall the WSL system component
Reboot
Update Docker Desktop
Reboot
Observer who the WSL system component is installed again
Stanzilla
commented
1 year ago
Actual behavior
The installer/updater for Docker Desktop keeps installing the WSL system component
Expected behavior
The system component is deprecated and all WSL installations in the future will be from the Microsoft Store. Docker Desktop should detect if the Microsoft Store version is installed and then not try to install the system component.
Information
Output of
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" checkDiagnostics output:
Starting diagnostics [PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [FAIL] DD0002: does the bootloader have virtualization enabled? contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:46:59.286830000Z][com.docker.diagnose.exe][I] ipc.NewClient: 247fb9e2-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service [2023-05-15T18:46:59.286830000Z][com.docker.diagnose.exe][I] (859389ec) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /hyperv/bootloader [2023-05-15T18:46:59.287419600Z][com.docker.diagnose.exe][W] (859389ec) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /hyperv/bootloader (589.6µs): Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:46:59.287925500Z][com.docker.diagnose.exe][I] (859389ec-1) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:46:59.287925500Z][com.docker.diagnose.exe][W] (859389ec-1) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:00.298116900Z][com.docker.diagnose.exe][I] (859389ec-2) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:00.298116900Z][com.docker.diagnose.exe][W] (859389ec-2) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:01.309133200Z][com.docker.diagnose.exe][I] (859389ec-3) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:01.309234900Z][com.docker.diagnose.exe][W] (859389ec-3) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (101.7µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:02.324701800Z][com.docker.diagnose.exe][I] (859389ec-4) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:02.325223900Z][com.docker.diagnose.exe][W] (859389ec-4) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:03.329428000Z][com.docker.diagnose.exe][I] (859389ec-5) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:03.329428000Z][com.docker.diagnose.exe][W] (859389ec-5) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:04.343544300Z][com.docker.diagnose.exe][I] (859389ec-6) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:04.343544300Z][com.docker.diagnose.exe][W] (859389ec-6) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:05.354218900Z][com.docker.diagnose.exe][I] (859389ec-7) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:05.354724100Z][com.docker.diagnose.exe][W] (859389ec-7) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (505.2µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:06.358133700Z][com.docker.diagnose.exe][I] (859389ec-8) 247fb9e2-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:06.358133700Z][com.docker.diagnose.exe][W] (859389ec-8) 247fb9e2-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [SKIP] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [FAIL] DD0022: is the Virtual Machine Platform Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:06.375442700Z][com.docker.diagnose.exe][I] ipc.NewClient: e40388cf-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service [2023-05-15T18:47:06.375962600Z][com.docker.diagnose.exe][I] (c5ebe26a) e40388cf-com.docker.diagnose C->S com.docker.service POST /windowsfeatures/check: [VirtualMachinePlatform (Virtual Machine Platform)] [2023-05-15T18:47:06.376486200Z][com.docker.diagnose.exe][W] (c5ebe26a) e40388cf-com.docker.diagnose C<-S NoResponse POST /windowsfeatures/check (523.6µs): Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:06.376486200Z][com.docker.diagnose.exe][I] (c5ebe26a-1) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:06.377001000Z][com.docker.diagnose.exe][W] (c5ebe26a-1) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (514.8µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:07.386488400Z][com.docker.diagnose.exe][I] (c5ebe26a-2) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:07.386994800Z][com.docker.diagnose.exe][W] (c5ebe26a-2) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (506.4µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:08.400404200Z][com.docker.diagnose.exe][I] (c5ebe26a-3) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:08.400909200Z][com.docker.diagnose.exe][W] (c5ebe26a-3) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (505µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:09.413116500Z][com.docker.diagnose.exe][I] (c5ebe26a-4) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:09.413235000Z][com.docker.diagnose.exe][W] (c5ebe26a-4) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (118.5µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:10.425977500Z][com.docker.diagnose.exe][I] (c5ebe26a-5) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:10.426493100Z][com.docker.diagnose.exe][W] (c5ebe26a-5) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (515.6µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:11.434871300Z][com.docker.diagnose.exe][I] (c5ebe26a-6) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:11.434871300Z][com.docker.diagnose.exe][W] (c5ebe26a-6) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:12.435872400Z][com.docker.diagnose.exe][I] (c5ebe26a-7) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:12.435872400Z][com.docker.diagnose.exe][W] (c5ebe26a-7) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:13.443641600Z][com.docker.diagnose.exe][I] (c5ebe26a-8) e40388cf-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:13.443742600Z][com.docker.diagnose.exe][W] (c5ebe26a-8) e40388cf-com.docker.diagnose C<-S NoResponse GET /ping (101µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [FAIL] DD0021: is the WSL 2 Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:13.444305100Z][com.docker.diagnose.exe][I] ipc.NewClient: 32abf756-com.docker.diagnose -> \\.\pipe\dockerBackendV2 com.docker.service [2023-05-15T18:47:13.444305100Z][com.docker.diagnose.exe][I] (22261ebe) 32abf756-com.docker.diagnose C->S com.docker.service POST /windowsfeatures/check: [Microsoft-Windows-Subsystem-Linux (Windows Subsystem for Linux)] [2023-05-15T18:47:13.444305100Z][com.docker.diagnose.exe][W] (22261ebe) 32abf756-com.docker.diagnose C<-S NoResponse POST /windowsfeatures/check (0s): Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:13.444305100Z][com.docker.diagnose.exe][I] (22261ebe-1) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:13.445255500Z][com.docker.diagnose.exe][W] (22261ebe-1) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (950.4µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:14.459044200Z][com.docker.diagnose.exe][I] (22261ebe-2) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:14.459044200Z][com.docker.diagnose.exe][W] (22261ebe-2) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:15.468417700Z][com.docker.diagnose.exe][I] (22261ebe-3) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:15.468922200Z][com.docker.diagnose.exe][W] (22261ebe-3) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (504.5µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:16.469524000Z][com.docker.diagnose.exe][I] (22261ebe-4) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:16.469524000Z][com.docker.diagnose.exe][W] (22261ebe-4) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (108.2µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:17.471886600Z][com.docker.diagnose.exe][I] (22261ebe-5) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:17.471886600Z][com.docker.diagnose.exe][W] (22261ebe-5) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:18.484599600Z][com.docker.diagnose.exe][I] (22261ebe-6) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:18.484599600Z][com.docker.diagnose.exe][W] (22261ebe-6) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:19.495379700Z][com.docker.diagnose.exe][I] (22261ebe-7) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:19.495884900Z][com.docker.diagnose.exe][W] (22261ebe-7) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (505.2µs): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:20.497375400Z][com.docker.diagnose.exe][I] (22261ebe-8) 32abf756-com.docker.diagnose C->S com.docker.service GET /ping [2023-05-15T18:47:20.497375400Z][com.docker.diagnose.exe][W] (22261ebe-8) 32abf756-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [PASS] DD0024: is WSL installed? [PASS] DD0025: are WSL distros installed? [FAIL] DD0026: is the WSL LxssManager service running? LxssManager service is not running [FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? [130374.746190] EXT4-fs error (device sdd): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal [FAIL] DD0035: is the VM time synchronized? parsing time output: 2023-05-15T18:47:20+00:00: parsing time "2023-05-15T18:47:20+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? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0013: is the $PATH ok? [PASS] DD0003: is the Docker CLI working? [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? [FAIL] DD0006: is the Docker Desktop Service responding? failed to ping com.docker.service with error: Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [2023-05-15T18:47:23.960639200Z][com.docker.diagnose.exe][I] ipc.NewClient: 7423d4d1-diagnose -> \\.\pipe\dockerBackendV2 Service [2023-05-15T18:47:23.961172000Z][com.docker.diagnose.exe][I] (0c73eb00) 7423d4d1-diagnose C->S Service GET /ping [2023-05-15T18:47:23.961172000Z][com.docker.diagnose.exe][W] (0c73eb00) 7423d4d1-diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [SKIP] DD0030: is the image access management authorized? [PASS] DD0033: does the host have Internet access? [WARN] DD0002: does the bootloader have virtualization enabled? contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [WARN] DD0022: is the Virtual Machine Platform Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [WARN] DD0021: is the WSL 2 Windows Feature enabled? querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. [PASS] DD0024: is WSL installed? [PASS] DD0025: are WSL distros installed? [WARN] DD0026: is the WSL LxssManager service running? LxssManager service is not running [WARN] DD0029: is the WSL 2 Linux filesystem corrupt? [130374.746190] EXT4-fs error (device sdd): ext4_put_super:1188: comm Xwayland: Couldn't clean up the journal [WARN] DD0035: is the VM time synchronized? parsing time output: 2023-05-15T18:47:20+00:00: parsing time "2023-05-15T18:47:20+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? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0032: do Docker networks overlap with host IPs? Please note the following 25 warnings: 1 : The check: does the bootloader have virtualization enabled? Produced the following warning: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled. Run: bcdedit /set hypervisorlaunchtype auto 2 : The check: does the bootloader have virtualization enabled? Produced the following warning: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled. Run: bcdedit /set hypervisorlaunchtype auto 3 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 4 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 5 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 6 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 7 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 8 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 9 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 10 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 11 : The check: is the WSL LxssManager service running? Produced the following warning: LxssManager service is not running The WSL LxssManager service must be running. Try running `sc config LxssManager start=auto` from an Administrator cmd.exe. 12 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 13 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 14 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 15 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 16 : The check: is the WSL 2 Linux filesystem corrupt? Produced the following warning: [130374.746190] EXT4-fs error (device sdd): ext4_put_super:1188: comm Xwayland: 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. 17 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 18 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 19 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 20 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 21 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 22 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 23 : The check: is the Virtual Machine Platform Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 24 : The check: is the WSL 2 Windows Feature enabled? Produced the following warning: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Microsoft-Windows-Subsystem-Linux Windows Feature is needed to run containers in WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 25 : The check: is the VM time synchronized? Produced the following warning: parsing time output: 2023-05-15T18:47:20+00:00: parsing time "2023-05-15T18:47:20+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". Please investigate the following 3 issues: 1 : The test: does the bootloader have virtualization enabled? Failed with: contacting Windows service: Get "http://ipc/hyperv/bootloader": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Docker engine runs inside a Linux VM. Therefore Windows must boot with the Microsoft Hypervisor enabled. Run: bcdedit /set hypervisorlaunchtype auto 2 : The test: is the Virtual Machine Platform Windows Feature enabled? Failed with: querying windows features: Post "http://ipc/windowsfeatures/check": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Virtual Machine Platform Windows Feature is needed to use WSL 2. See https://docs.microsoft.com/en-us/windows/wsl/install-win10 3 : The test: is the Docker Desktop Service responding? Failed with: failed to ping com.docker.service with error: Get "http://ipc/ping": open \\.\pipe\dockerBackendV2: The system cannot find the file specified. The Docker Desktop Service is needed to start the Docker engine. Open the list of Services and configure the Docker Desktop Service to start automatically.Specifically this part is the problem:
Steps to reproduce the behavior