You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ID of diagnostic
56D861CA-DEA2-480B-B7C6-D3391E401313/20241203213911
ERROR MESSAGE
deploying WSL2 distributions
ensuring main distro is deployed: deploying "docker-desktop": importing WSL distro "WSL2 is not supported with your current machine configuration.\r\nPlease enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS.\r\nEnable "Virtual Machine Platform" by running: wsl.exe --install --no-distribution\r\nFor information please visit https://aka.ms/enablevirtualization\r\nError code: Wsl/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED\r\n" output="docker-desktop": exit code: 4294967295: running WSL command wsl.exe C:\WINDOWS\System32\wsl.exe --import docker-desktop \AppData\Local\Docker\wsl\main C:\Program Files\Docker\Docker\resources\wsl\wsl-bootstrap.tar --version 2: WSL2 is not supported with your current machine configuration.
Please enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS.
Enable "Virtual Machine Platform" by running: wsl.exe --install --no-distribution
For information please visit https://aka.ms/enablevirtualization
Error code: Wsl/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED
: exit status 0xffffffff
checking if isocache exists: CreateFile \wsl$\docker-desktop-data\isocache: The network name cannot be found.
POWER SHELL DIAGNOSTIC : WSL Distribution docker-desktop is missing
[2024-12-03T21:41:12.975181200Z][com.docker.diagnose.exe.ipc] cf40f34c-diagnose -> \.\pipe\dockerBackendApiServer BackendAPI
[2024-12-03T21:41:12.980170500Z][com.docker.diagnose.exe.ipc] (71947a32) cf40f34c-diagnose C->S BackendAPI POST /idle/make-busy
[2024-12-03T21:41:12.981385600Z][com.docker.diagnose.exe.ipc] (71947a32) cf40f34c-diagnose C<-S 71c1bb71-BackendAPI POST /idle/make-busy (1.2151ms): 0xc00054c320
[2024-12-03T21:41:13.981542200Z][com.docker.diagnose.exe.ipc] (71947a32-1) cf40f34c-diagnose C->S BackendAPI GET /idle
[2024-12-03T21:41:13.985053500Z][com.docker.diagnose.exe.ipc] (71947a32-1) cf40f34c-diagnose C<-S 71c1bb71-BackendAPI GET /idle (3.5113ms): {"apisInFlight":{"/v1.43/containers/json from Go-http-client/1.1":1},"busyReason":["1 calls to /v1.43/containers/json from Go-http-client/1.1","timed activities: map[/idle/make-busy:28996367400]"],"timedActivities":{"/idle/make-busy":28996367400},"vmRunning":true}
[PASS] DD0027: is there available disk space on the host?
[SKIP] 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?
[FAIL] DD0025: are WSL distros installed? WSL Distribution docker-desktop is missing
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? prereq failed: are WSL distros installed?
[FAIL] DD0035: is the VM time synchronized? prereq failed: are WSL distros installed?
[FAIL] DD0017: can a VM be started? prereq failed: are WSL distros installed?
[FAIL] DD0016: is the LinuxKit VM running? prereq failed: can a VM be started?
[FAIL] DD0004: is the Docker engine running? prereq failed: is the LinuxKit VM 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] DD0037: 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?
[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?
[WARN] DD0025: are WSL distros installed? WSL Distribution docker-desktop is missing
[PASS] DD0026: is the WSL LxssManager service running?
[WARN] DD0029: is the WSL 2 Linux filesystem corrupt? prereq failed: are WSL distros installed?
[WARN] DD0035: is the VM time synchronized? prereq failed: are WSL distros installed?
[WARN] DD0017: can a VM be started? prereq failed: are WSL distros installed?
[WARN] DD0016: is the LinuxKit VM running? prereq failed: can a VM be started?
[WARN] DD0004: is the Docker engine running? prereq failed: is the LinuxKit VM 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?
Please note the following 10 warnings:
1 : The check: are WSL distros installed?
Produced the following warning: WSL Distribution docker-desktop is missing
The Docker engine uses several WSL distributions. Therefore these must be installed.
2 : The check: are WSL distros installed?
Produced the following warning: WSL Distribution docker-desktop is missing
The Docker engine uses several WSL distributions. Therefore these must be installed.
3 : The check: is the WSL 2 Linux filesystem corrupt?
Produced the following warning: prereq failed: are WSL distros installed?
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.
4 : The check: are WSL distros installed?
Produced the following warning: WSL Distribution docker-desktop is missing
The Docker engine uses several WSL distributions. Therefore these must be installed.
5 : The check: is the VM time synchronized?
Produced the following warning: prereq failed: are WSL distros installed?
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".
6 : The check: can a VM be started?
Produced the following warning: prereq failed: are WSL distros installed?
The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.
7 : The check: is the LinuxKit VM running?
Produced the following warning: prereq failed: can a VM be started?
The Docker engine runs inside a Linux VM. Therefore the VM must be running.
8 : The check: is the Docker engine running?
Produced the following warning: prereq failed: is the LinuxKit VM running?
The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.
9 : The check: does the Docker API work?
Produced the following warning: prereq failed: is the Docker engine running?
If the Docker API is not available from the host then Docker Desktop will not work correctly.
10 : The check: do Docker networks overlap with host IPs?
Produced the following warning: prereq failed: does the Docker API work?
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.
the key information in your error message is the following error: Wsl/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED.
This shows that you don't have the Windows components required to run the Microsoft Windows Subsystem for Linux (WSL2), which Docker Desktop depends on.
There are several suggested solutions on the web if you search for that error string, but I'd recommend to first try to get WSL2 working following Microsoft's docs or manually installing the latest WSL2 distribution from here. Please, note that administrator rights may be required.
Hello Andrea. Many thanks for fast reply. I already tried the manuel installation of wsl2 as you proposed but without success. We will explore your additional proposition. Best regards, Antoine
Docker Desktop - Unexpected WSL error
An unexpected error occurred while executing a WSL command.
Either shut down WSL down with wsl --shutdown, and/or reboot your machine. You can also try reinstalling WSL and/or Docker Desktop. If the issue persists,
Description
ID of diagnostic
56D861CA-DEA2-480B-B7C6-D3391E401313/20241203213911
ERROR MESSAGE
deploying WSL2 distributions
ensuring main distro is deployed: deploying "docker-desktop": importing WSL distro "WSL2 is not supported with your current machine configuration.\r\nPlease enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS.\r\nEnable "Virtual Machine Platform" by running: wsl.exe --install --no-distribution\r\nFor information please visit https://aka.ms/enablevirtualization\r\nError code: Wsl/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED\r\n" output="docker-desktop": exit code: 4294967295: running WSL command wsl.exe C:\WINDOWS\System32\wsl.exe --import docker-desktop \AppData\Local\Docker\wsl\main C:\Program Files\Docker\Docker\resources\wsl\wsl-bootstrap.tar --version 2: WSL2 is not supported with your current machine configuration.
Please enable the "Virtual Machine Platform" optional component and ensure virtualization is enabled in the BIOS.
Enable "Virtual Machine Platform" by running: wsl.exe --install --no-distribution
For information please visit https://aka.ms/enablevirtualization
Error code: Wsl/Service/RegisterDistro/CreateVm/HCS/HCS_E_HYPERV_NOT_INSTALLED
: exit status 0xffffffff
checking if isocache exists: CreateFile \wsl$\docker-desktop-data\isocache: The network name cannot be found.
POWER SHELL DIAGNOSTIC : WSL Distribution docker-desktop is missing
Try the new cross-platform PowerShell https://aka.ms/pscore6
PS C:\Users\Administrator> & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
Starting diagnostics
[2024-12-03T21:41:12.975181200Z][com.docker.diagnose.exe.ipc] cf40f34c-diagnose -> \.\pipe\dockerBackendApiServer BackendAPI
[2024-12-03T21:41:12.980170500Z][com.docker.diagnose.exe.ipc] (71947a32) cf40f34c-diagnose C->S BackendAPI POST /idle/make-busy
[2024-12-03T21:41:12.981385600Z][com.docker.diagnose.exe.ipc] (71947a32) cf40f34c-diagnose C<-S 71c1bb71-BackendAPI POST /idle/make-busy (1.2151ms): 0xc00054c320
[2024-12-03T21:41:13.981542200Z][com.docker.diagnose.exe.ipc] (71947a32-1) cf40f34c-diagnose C->S BackendAPI GET /idle
[2024-12-03T21:41:13.985053500Z][com.docker.diagnose.exe.ipc] (71947a32-1) cf40f34c-diagnose C<-S 71c1bb71-BackendAPI GET /idle (3.5113ms): {"apisInFlight":{"/v1.43/containers/json from Go-http-client/1.1":1},"busyReason":["1 calls to /v1.43/containers/json from Go-http-client/1.1","timed activities: map[/idle/make-busy:28996367400]"],"timedActivities":{"/idle/make-busy":28996367400},"vmRunning":true}
[PASS] DD0027: is there available disk space on the host?
[SKIP] 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?
[FAIL] DD0025: are WSL distros installed? WSL Distribution docker-desktop is missing
[PASS] DD0026: is the WSL LxssManager service running?
[FAIL] DD0029: is the WSL 2 Linux filesystem corrupt? prereq failed: are WSL distros installed?
[FAIL] DD0035: is the VM time synchronized? prereq failed: are WSL distros installed?
[FAIL] DD0017: can a VM be started? prereq failed: are WSL distros installed?
[FAIL] DD0016: is the LinuxKit VM running? prereq failed: can a VM be started?
[FAIL] DD0004: is the Docker engine running? prereq failed: is the LinuxKit VM 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] DD0037: 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?
[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?
[WARN] DD0025: are WSL distros installed? WSL Distribution docker-desktop is missing
[PASS] DD0026: is the WSL LxssManager service running?
[WARN] DD0029: is the WSL 2 Linux filesystem corrupt? prereq failed: are WSL distros installed?
[WARN] DD0035: is the VM time synchronized? prereq failed: are WSL distros installed?
[WARN] DD0017: can a VM be started? prereq failed: are WSL distros installed?
[WARN] DD0016: is the LinuxKit VM running? prereq failed: can a VM be started?
[WARN] DD0004: is the Docker engine running? prereq failed: is the LinuxKit VM 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?
Please note the following 10 warnings:
1 : The check: are WSL distros installed?
Produced the following warning: WSL Distribution docker-desktop is missing
The Docker engine uses several WSL distributions. Therefore these must be installed.
2 : The check: are WSL distros installed?
Produced the following warning: WSL Distribution docker-desktop is missing
The Docker engine uses several WSL distributions. Therefore these must be installed.
3 : The check: is the WSL 2 Linux filesystem corrupt?
Produced the following warning: prereq failed: are WSL distros installed?
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.
4 : The check: are WSL distros installed?
Produced the following warning: WSL Distribution docker-desktop is missing
The Docker engine uses several WSL distributions. Therefore these must be installed.
5 : The check: is the VM time synchronized?
Produced the following warning: prereq failed: are WSL distros installed?
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".
6 : The check: can a VM be started?
Produced the following warning: prereq failed: are WSL distros installed?
The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.
7 : The check: is the LinuxKit VM running?
Produced the following warning: prereq failed: can a VM be started?
The Docker engine runs inside a Linux VM. Therefore the VM must be running.
8 : The check: is the Docker engine running?
Produced the following warning: prereq failed: is the LinuxKit VM running?
The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.
9 : The check: does the Docker API work?
Produced the following warning: prereq failed: is the Docker engine running?
If the Docker API is not available from the host then Docker Desktop will not work correctly.
10 : The check: do Docker networks overlap with host IPs?
Produced the following warning: prereq failed: does the Docker API work?
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: are WSL distros installed?
Failed with: WSL Distribution docker-desktop is missing
The Docker engine uses several WSL distributions. Therefore these must be installed.
PS C:\Users\Administrator>
Reproduce
docker desktop run
Expected behavior
No response
docker version
docker info
?
Diagnostics ID
56D861CA-DEA2-480B-B7C6-D3391E401313/20241203213911
Additional Info
No response
The text was updated successfully, but these errors were encountered: