WSL2 Not Installed-Recognized With Docker Desktop For Windows

Anonymous
2024-04-21T15:53:31+00:00

When I try to run Docker it gives me this

Unexpected WSL Error

Ive done troubleshooting
Ive reset the docker
The updates are made
Theyre all the latest version

Microsoft Windows [Version 10.0.19045.4291]
Deployment Image Servicing and Management tool

Version: 10.0.19041.3636

Image Version: 10.0.19045.4291

Enabling feature(s)

[==========================100.0%==========================]

The operation completed successfully.

C:\WINDOWS\system32>wsl --version

WSL version: 2.1.5.0

Kernel version: 5.15.146.1-2

WSLg version: 1.0.60

MSRDC version: 1.2.5105

Direct3D version: 1.611.1-81528511

DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp

Windows version: 10.0.19045.4291

C:\WINDOWS\system32>wsl.exe --update

Checking for updates.

The most recent version of Windows Subsystem for Linux is already installed.

WSL2 because Hypervisor -v wasnt found

So i enabled it in BIOS and on Windows and I opened Docker again and I got an error

unexpected WSl error while executing wsl command

But the previous error did not show up but:

C:\Program Files\Docker\Docker>com.docker.diagnose.exe check
Starting diagnostics

[2024-04-21T07:12:34.475864600Z][com.docker.diagnose.exe.ipc][I] ipc.NewClient: d99467e7-diagnose -> .\pipe\dockerBackendApiServer BackendAPI
[2024-04-21T07:12:34.481864500Z][com.docker.diagnose.exe.ipc][I] (9574e3f1) d99467e7-diagnose C->S BackendAPI POST /idle/make-busy
[2024-04-21T07:12:34.483863400Z][com.docker.diagnose.exe.ipc][W] (9574e3f1) d99467e7-diagnose C<-S NoResponse POST /idle/make-busy (1.9989ms): Post "http://ipc/idle/make-busy": open .\pipe\dockerBackendApiServer: The system cannot find the file specified.
[2024-04-21T07:12:35.483824900Z][com.docker.diagnose.exe.ipc][I] (af8f1724) d99467e7-diagnose C->S BackendAPI GET /idle
[2024-04-21T07:12:35.484730600Z][com.docker.diagnose.exe.ipc][W] (af8f1724) d99467e7-diagnose C<-S NoResponse GET /idle (905.7µs): Get "http://ipc/idle": open .\pipe\dockerBackendApiServer: The system cannot find the file specified.
[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?
[FAIL] DD0001: is the application running? Docker is not running
[SKIP] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[SKIP] DD0021: is the WSL 2 Windows Feature enabled?
[FAIL] DD0024: is WSL installed? exec: "wsl": executable file not found in %PATH%
[FAIL] DD0025: are WSL distros installed? prereq failed: is WSL installed?
[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: is WSL installed?
[FAIL] DD0017: can a VM be started? prereq failed: is WSL installed?
[FAIL] DD0016: is the LinuxKit VM running? prereq failed: is the application running?
[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?
[FAIL] DD0013: is the $PATH ok? unable to find docker executable on PATH
[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?
[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?
[WARN] 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?
[WARN] DD0024: is WSL installed? exec: "wsl": executable file not found in %PATH%
[WARN] DD0025: are WSL distros installed? prereq failed: is WSL installed?
[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: is WSL installed?
[WARN] DD0017: can a VM be started? prereq failed: is WSL installed?
[WARN] DD0016: is the LinuxKit VM running? prereq failed: is the application running?
[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?something went wrong error

The factory reset couldnt be completed successfully and cleaning up distro Ubuntu and output and starting shell: exec wsl.exe executable file not found in the path

I then deleted the settings and restarted to default
Docker loaded and stopped

Please note the following 17 warnings:

1 : The check: is the application running?
Produced the following warning: Docker is not running

Is the Docker Desktop application running?

2 : The check: is WSL installed?
Produced the following warning: exec: "wsl": executable file not found in %PATH%

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

3 : The check: is WSL installed?
Produced the following warning: exec: "wsl": executable file not found in %PATH%

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

4 : The check: are WSL distros installed?
Produced the following warning: prereq failed: is WSL installed?

The Docker engine uses several WSL distributions. Therefore these must be installed.

5 : The check: is WSL installed?
Produced the following warning: exec: "wsl": executable file not found in %PATH%

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

6 : The check: are WSL distros installed?
Produced the following warning: prereq failed: is WSL installed?

The Docker engine uses several WSL distributions. Therefore these must be installed.

7 : 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:
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.

8 : The check: is WSL installed?
Produced the following warning: exec: "wsl": executable file not found in %PATH%

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

9 : The check: is WSL installed?
Produced the following warning: exec: "wsl": executable file not found in %PATH%

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

10 : The check: are WSL distros installed?
Produced the following warning: prereq failed: is WSL installed?

The Docker engine uses several WSL distributions. Therefore these must be installed.

11 : The check: is the VM time synchronized?
Produced the following warning: prereq failed: is WSL 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".

12 : The check: can a VM be started?
Produced the following warning: prereq failed: is WSL installed?

The Docker engine runs inside a Linux VM. Therefore we must be able to start Virtual Machines.

13 : The check: is the LinuxKit VM running?
Produced the following warning: prereq failed: is the application running?

The Docker engine runs inside a Linux VM. Therefore the VM must be running.

14 : The check: are the LinuxKit services running?
Produced the following warning: prereq failed: is the LinuxKit VM running?

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

15 : The check: is the Docker engine running?
Produced the following warning: prereq failed: are the LinuxKit services running?

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

16 : 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.

17 : 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 3 issues:

1 : The test: is the application running?
Failed with: Docker is not running

Is the Docker Desktop application running?

2 : The test: is WSL installed?
Failed with: exec: "wsl": executable file not found in %PATH%

The Docker engine runs inside a WSL environment. Therefore WSL must be installed. Try running wsl --status.

3 : The test: is the $PATH ok?
Failed with: unable to find docker executable on PATH

The directory containing the docker CLI tools must be on the $PATH

C:\Program Files\Docker\Docker>

The program is in the variables

First i show you Docker installed:

Directory of C:\Program Files\Docker\Docker

04/20/2024 05:51 PM <DIR> .
04/20/2024 05:51 PM <DIR> ..
04/20/2024 05:48 PM 4,607 app.json
04/20/2024 05:49 PM 31,832 BITSReference5_0.dll
04/20/2024 05:48 PM 20,072 com.docker.service
04/20/2024 05:48 PM 19,072 com.docker.service.config
04/20/2024 05:48 PM 28,160 com.docker.service.pdb
04/20/2024 05:49 PM 1,734,744 courgette64.exe
04/20/2024 05:49 PM 7,269,992 Docker Desktop Installer.exe
04/20/2024 05:48 PM 19,431 Docker Desktop Installer.exe.config
04/20/2024 05:48 PM 382,464 Docker Desktop Installer.pdb
04/20/2024 05:49 PM 2,347,080 Docker Desktop.exe
04/20/2024 05:49 PM 106,072 Docker.Backend.dll
04/20/2024 05:48 PM 232,960 Docker.Backend.pdb
04/20/2024 05:49 PM 160,856 Docker.Core.dll
04/20/2024 05:48 PM 476,672 Docker.Core.pdb
04/20/2024 05:49 PM 12,215,888 DockerCli.exe
04/20/2024 05:49 PM <DIR> frontend
04/20/2024 05:49 PM 23,128 HttpOverStream.Client.dll
04/20/2024 05:49 PM 25,688 HttpOverStream.dll
04/20/2024 05:49 PM 27,224 HttpOverStream.NamedPipe.dll
04/20/2024 05:49 PM 29,272 HttpOverStream.Server.Owin.dll
04/20/2024 05:51 PM 4,607 installationmanifest.json
04/20/2024 05:49 PM 46,176 InstallerCli.exe
04/20/2024 05:48 PM 19,072 InstallerCli.exe.config
04/20/2024 05:48 PM 75,264 InstallerCli.pdb
04/20/2024 05:49 PM 101,464 Microsoft.Owin.dll
04/20/2024 05:49 PM 66,136 Microsoft.Owin.Hosting.dll
04/20/2024 05:49 PM 31,320 Microsoft.Virtualization.Client.Common.Types.dll
04/20/2024 05:49 PM 1,631,832 Microsoft.Virtualization.Client.Management.dll
04/20/2024 05:49 PM 15,448 Microsoft.Win32.Primitives.dll
04/20/2024 05:49 PM 60,504 Microsoft.Windows.ComputeVirtualization.dll
04/20/2024 05:49 PM 92,760 netstandard.dll
04/20/2024 05:49 PM 704,600 Newtonsoft.Json.dll
04/20/2024 05:49 PM 866,392 NLog.dll
04/20/2024 05:49 PM 14,936 Owin.dll
04/20/2024 05:50 PM <DIR> resources
04/20/2024 05:50 PM 27,224 SimCim.Core.dll
04/20/2024 05:50 PM 473,688 SimCim.Root.StandardCimV2.dll
04/20/2024 05:50 PM 2,086,488 SimCim.Root.V2.dll
04/20/2024 05:50 PM 518,744 SimCim.Root.Virtualization.V2.dll
04/20/2024 05:50 PM 15,448 System.AppContext.dll
04/20/2024 05:50 PM 15,448 System.Collections.Concurrent.dll
04/20/2024 05:50 PM 15,960 System.Collections.dll
04/20/2024 05:50 PM 15,448 System.Collections.NonGeneric.dll
04/20/2024 05:50 PM 15,448 System.Collections.Specialized.dll
04/20/2024 05:50 PM 15,448 System.ComponentModel.dll
04/20/2024 05:50 PM 15,960 System.ComponentModel.EventBasedAsync.dll
04/20/2024 05:50 PM 15,960 System.ComponentModel.Primitives.dll
04/20/2024 05:50 PM 16,984 System.ComponentModel.TypeConverter.dll
04/20/2024 05:50 PM 15,448 System.Console.dll
04/20/2024 05:50 PM 148,568 System.Data.Common.dll
04/20/2024 05:50 PM 15,960 System.Diagnostics.Contracts.dll
04/20/2024 05:50 PM 15,448 System.Diagnostics.Debug.dll
04/20/2024 05:50 PM 29,784 System.Diagnostics.DiagnosticSource.dll
04/20/2024 05:50 PM 15,448 System.Diagnostics.FileVersionInfo.dll
04/20/2024 05:50 PM 15,960 System.Diagnostics.Process.dll
04/20/2024 05:50 PM 18,008 System.Diagnostics.StackTrace.dll
04/20/2024 05:50 PM 15,448 System.Diagnostics.TextWriterTraceListener.dll
04/20/2024 05:50 PM 15,448 System.Diagnostics.Tools.dll
04/20/2024 05:50 PM 15,960 System.Diagnostics.TraceSource.dll
04/20/2024 05:50 PM 25,688 System.Diagnostics.Tracing.dll
04/20/2024 05:50 PM 15,448 System.Drawing.Primitives.dll
04/20/2024 05:50 PM 16,472 System.Dynamic.Runtime.dll
04/20/2024 05:50 PM 15,960 System.Globalization.Calendars.dll
04/20/2024 05:50 PM 15,448 System.Globalization.dll
04/20/2024 05:50 PM 20,056 System.Globalization.Extensions.dll
04/20/2024 05:50 PM 105,048 System.IO.Compression.dll
04/20/2024 05:50 PM 15,448 System.IO.Compression.ZipFile.dll
04/20/2024 05:50 PM 15,448 System.IO.dll
04/20/2024 05:50 PM 15,448 System.IO.FileSystem.dll
04/20/2024 05:50 PM 15,448 System.IO.FileSystem.DriveInfo.dll
04/20/2024 05:50 PM 15,448 System.IO.FileSystem.Primitives.dll
04/20/2024 05:50 PM 15,448 System.IO.FileSystem.Watcher.dll
04/20/2024 05:50 PM 15,448 System.IO.IsolatedStorage.dll
04/20/2024 05:50 PM 15,448 System.IO.MemoryMappedFiles.dll
04/20/2024 05:50 PM 15,448 System.IO.Pipes.dll
04/20/2024 05:50 PM 15,448 System.IO.UnmanagedMemoryStream.dll
04/20/2024 05:50 PM 15,448 System.Linq.dll
04/20/2024 05:50 PM 16,472 System.Linq.Expressions.dll
04/20/2024 05:50 PM 15,448 System.Linq.Parallel.dll
04/20/2024 05:50 PM 15,448 System.Linq.Queryable.dll
04/20/2024 05:50 PM 370,776 System.Management.Automation.dll
04/20/2024 05:50 PM 192,600 System.Net.Http.dll
04/20/2024 05:50 PM 179,800 System.Net.Http.Formatting.dll
04/20/2024 05:50 PM 33,880 System.Net.IPNetwork.dll
04/20/2024 05:50 PM 15,448 System.Net.NameResolution.dll
04/20/2024 05:50 PM 16,472 System.Net.NetworkInformation.dll
04/20/2024 05:50 PM 15,448 System.Net.Ping.dll
04/20/2024 05:50 PM 16,472 System.Net.Primitives.dll
04/20/2024 05:50 PM 15,448 System.Net.Requests.dll
04/20/2024 05:50 PM 15,960 System.Net.Security.dll
04/20/2024 05:50 PM 24,664 System.Net.Sockets.dll
04/20/2024 05:50 PM 15,448 System.Net.WebHeaderCollection.dll
04/20/2024 05:50 PM 15,448 System.Net.WebSockets.Client.dll
04/20/2024 05:50 PM 15,448 System.Net.WebSockets.dll
04/20/2024 05:50 PM 15,960 System.ObjectModel.dll
04/20/2024 05:50 PM 109,656 System.Reactive.Core.dll
04/20/2024 05:50 PM 1,268,312 System.Reactive.dll
04/20/2024 05:50 PM 16,472 System.Reactive.Interfaces.dll
04/20/2024 05:50 PM 16,984 System.Reactive.Linq.dll
04/20/2024 05:50 PM 16,472 System.Reflection.dll
04/20/2024 05:50 PM 15,448 System.Reflection.Extensions.dll
04/20/2024 05:50 PM 15,960 System.Reflection.Primitives.dll
04/20/2024 05:50 PM 15,448 System.Resources.Reader.dll
04/20/2024 05:50 PM 15,448 System.Resources.ResourceManager.dll
04/20/2024 05:50 PM 15,448 System.Resources.Writer.dll
04/20/2024 05:50 PM 18,008 System.Runtime.CompilerServices.Unsafe.dll
04/20/2024 05:50 PM 15,960 System.Runtime.CompilerServices.VisualC.dll
04/20/2024 05:50 PM 23,640 System.Runtime.dll
04/20/2024 05:50 PM 15,960 System.Runtime.Extensions.dll
04/20/2024 05:50 PM 15,448 System.Runtime.Handles.dll
04/20/2024 05:50 PM 18,520 System.Runtime.InteropServices.dll
04/20/2024 05:50 PM 22,616 System.Runtime.InteropServices.RuntimeInformation.dll
04/20/2024 05:50 PM 15,448 System.Runtime.Numerics.dll
04/20/2024 05:50 PM 15,448 System.Runtime.Serialization.Formatters.dll
04/20/2024 05:50 PM 15,448 System.Runtime.Serialization.Json.dll
04/20/2024 05:50 PM 21,080 System.Runtime.Serialization.Primitives.dll
04/20/2024 05:50 PM 19,032 System.Runtime.Serialization.Xml.dll
04/20/2024 05:50 PM 15,448 System.Security.Claims.dll
04/20/2024 05:50 PM 41,048 System.Security.Cryptography.Algorithms.dll
04/20/2024 05:50 PM 15,448 System.Security.Cryptography.Csp.dll
04/20/2024 05:50 PM 15,448 System.Security.Cryptography.Encoding.dll
04/20/2024 05:50 PM 15,960 System.Security.Cryptography.Primitives.dll
04/20/2024 05:50 PM 16,984 System.Security.Cryptography.X509Certificates.dll
04/20/2024 05:50 PM 15,448 System.Security.Principal.dll
04/20/2024 05:50 PM 16,472 System.Security.SecureString.dll
04/20/2024 05:50 PM 15,960 System.Text.Encoding.dll
04/20/2024 05:50 PM 15,448 System.Text.Encoding.Extensions.dll
04/20/2024 05:50 PM 15,448 System.Text.RegularExpressions.dll
04/20/2024 05:50 PM 16,472 System.Threading.dll
04/20/2024 05:50 PM 31,832 System.Threading.Overlapped.dll
04/20/2024 05:50 PM 16,472 System.Threading.Tasks.dll
04/20/2024 05:50 PM 27,224 System.Threading.Tasks.Extensions.dll
04/20/2024 05:50 PM 15,448 System.Threading.Tasks.Parallel.dll
04/20/2024 05:50 PM 15,448 System.Threading.Thread.dll
04/20/2024 05:50 PM 15,448 System.Threading.ThreadPool.dll
04/20/2024 05:50 PM 15,448 System.Threading.Timer.dll
04/20/2024 05:50 PM 73,304 System.ValueTuple.dll
04/20/2024 05:50 PM 456,280 System.Web.Http.dll
04/20/2024 05:50 PM 62,552 System.Web.Http.Owin.dll
04/20/2024 05:50 PM 15,960 System.Xml.ReaderWriter.dll
04/20/2024 05:50 PM 15,960 System.Xml.XDocument.dll
04/20/2024 05:50 PM 15,960 System.Xml.XmlDocument.dll
04/20/2024 05:50 PM 15,960 System.Xml.XmlSerializer.dll
04/20/2024 05:50 PM 15,448 System.Xml.XPath.dll
04/20/2024 05:50 PM 16,984 System.Xml.XPath.XDocument.dll
143 File(s) 36,609,709 bytes

when i tried to run installercli it told me i cant run it on my pc WHY??

\Program Files\WSL>wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu (Default)

C:\Program Files\WSL>wsl --list --verbose
NAME STATE VERSION

  • Ubuntu Stopped 1

C:\Program Files\WSL>wsl --status
Default Distribution: Ubuntu
Default Version: 2

C:\Program Files\WSL>C:\Program Files\WSL>wsl
Welcome to Ubuntu 22.04.3 LTS (GNU/Linux 4.4.0-19041-Microsoft x86_64)so why did it work by me running wsl in dos and not docker desktop running it on its own and not finding it installed? THENN
I install and run Podman Desktop that it needs

WSL version should be >= 1.2.5
YET I HAVE THE LATEST VERSION

Virtual Machine Platform should be enabled to be able to run Podman.
WHICH IT IS

Could not detect WSL2

I HAVE SPENT 2 DAYS TRYING TO FIGURE THIS OUT AND KEEP GETTING ERRORS
I HAVE HP ELITE 8300 SFF I7-3770 3.4GHZ
16GB RAM

Windows for business Windows Server Devices and deployment Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2024-04-22T02:27:51+00:00

    Hello

    Thank you for posting in Microsoft Community forum.

    Based on the description, I understand your question is related to the WSL and Docker.

    Since there are no engineers dedicated to WSL and Docker in this forum. in order to be able to get a quick and effective handling of your issue, I recommend that you repost your question in the Q&A forum, where there will be a dedicated engineer to give you a professional and effective reply.

    Here is the link for Q&A forum.

    Questions - Microsoft Q&A

    Click the "Ask a Question" button in the upper right corner to post your question and select any tags related to your productions.

    Thank you for your understanding and support. If you have any question or concern, please feel free to let us know.

    Have a nice day.

    Best Regards,

    Molly

    0 comments No comments