Cannot start Docket Desktop on windows (timeout while waiting for WSL integration agent) #13461
Comments
|
Hi @lakshman503, sorry you hit a problem but thanks for filing the issue. Looking at the diagnosis you posted, this is likely a duplicate of #13445 . Could you please let us know the output of Thanks. |
Yes, we are working on it. Docker Desktop 4.19 needs to know the version of WSL on the host, but unfortunately older versions of WSL do not support the As a work-around, updating WSL to the latest version ( |
|
Hi Cesar,
I tried getting the wsl version using (wsl --version) from powershell.
Please find the below screenshot on the same.
[image: image.png]
After that as per your above email I tried executing (wsl --update). Please
find the below screenshot on the same.
[image: image.png]
After this I tried to start docker desktop again. But still the error is
the same as before. "Unexpected WSL error".
[image: image.png]
Please resolve this issue as soon as possible.
…On Sun, May 7, 2023 at 11:49 PM Cesar Talledo ***@***.***> wrote:
wow every time there is an update, docker breaks. seriously this is
annoygin fix it please
Yes, we are working on it. Docker Desktop 4.19 needs to know the version
of WSL on the host, but unfortunately older versions of WSL do not support
the --version flag. Docker Desktop knows this, but there is a bug in the
way it detects these older version.
As a work-around, updating WSL to the latest version (wsl --update) will
likely cause Docker Desktop 4.19 to start without problem.
—
Reply to this email directly, view it on GitHub
<#13461 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7UANRYUPFLE2RNKT2U3MFDXE7RUFANCNFSM6AAAAAAXWXBVSM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Best Regards,
T.V.S.S.Lakshmana Murthy,
+91-9542250311.
|
|
Hi @lakshman503, thank you very much for the response, but I don't see the attached images. Could you attach them directly to this issue. Thanks again! |
|
Hi Cesar,
PFA
[image: 1.png][image: 2.png][image: 3.png]
…On Mon, May 8, 2023 at 10:12 PM Cesar Talledo ***@***.***> wrote:
Hi @lakshman503 <https://github.com/lakshman503>, thank you very much for
the response, but I don't see the attached images. Could you attach them
directly to this issue.
Thanks again!
—
Reply to this email directly, view it on GitHub
<#13461 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7UANR64D5K6EKTZJ3IVUGDXFEO6NANCNFSM6AAAAAAXWXBVSM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
Best Regards,
T.V.S.S.Lakshmana Murthy,
+91-9542250311.
|
|
I do have this issue and had this output: |
|
Hi @lakshman503, unfortunately the images are still not attached; seems like you are responding on an email client and the attachments are getting dropped by GitHub. If possible please attach them in this GitHub issue directly. |
|
Hi @Francisco-madrid-gambin, sorry to hear and thanks for commenting. There are a couple of reasons why Docker Desktop may not start on Windows with WSL. If you have a chance, please upload a diagnostics bundle so we can take a look at how it fails in your case and give you the best solution. |
|
Hi @ctalledo, PFA
|
|
Hi @lakshman503, thanks for posting the attachments, very helpful. Question: what changed between the 1st and 3rd images above? How come |
|
Hi @ctalledo Initially I tried executing wsl --version then I got Invalid command line option --version. After that I tried executing wsl --update it got updated. After that again I tried to execute wsl --version then I can able to see the output from that command. After that I tried to start docker desktop again. but issue is same on it. It didnt change. |
|
Hi @lakshman503, thanks again for the response, it's helpful for us to debug.
Oh got it; the 3rd image above is from before you updated WSL. The first image above is after you updated WSL.
So looking at the 2nd image above, looks like it fails with "timeout while waiting for WSL integration agent" (and this means it's not a duplicate of #13445 as I originally thought). As a temporary work-around, try the following please. In the Docker settings.json file ( Then start Docker Desktop. If that works (i.e., Docker Desktop starts normally), then re-enable WSL integration via "Settings->Resources->WSL Integration". Then go to your WSL distro and type If things don't work, please let me know the error you are seeing to help us root-cause the problem. Thanks again, appreciate your help! |
ctalledo
changed the title
|
There is a memory leak issue with docker desktop since years ago. If your computer have not much ram available then maybe the memory leak will kick it faster and your docker will not even start. or if starts it will corrupt because it will fill ram quickily and then shutoff. Highly recommend switching to docker desktop hyper V but keep in mind this will sacrifice a part of your system resources all time and not use resources on demand as wsl2 integration was supposed to do. Sadly we need to make this issue more known so the devs focus 100% on it. |
Hi @samuk190, we are working hard on improving DD's memory usage on WSL, but this particular issue has nothing to do with memory consumption. It's strictly a problem with parsing the WSL version info. |
Actual behavior
When I start Docker Desktop it is showing like "wsl --shutdown" and start again. After executing wsl --shutdown also Docker desktop is showing same error again.
Expected behavior
Docker Desktop should start
Information
NoOutput of
& "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" checkPS C:\Program Files\Docker\Docker\resources> .\com.docker.diagnose.exe check
[2023-05-05T06:19:38.557187100Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics
[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[SKIP] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[SKIP] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[SKIP] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[2023-05-05T06:19:51.158679900Z][com.docker.diagnose.exe][I] ipc.NewClient: 2d56ceee-diagnose -> \.\pipe\dockerDiagnosticd diagnosticsd
[2023-05-05T06:19:51.169807300Z][com.docker.diagnose.exe][I] (dc1226fa) 2d56ceee-diagnose C->S diagnosticsd GET /ping
[2023-05-05T06:19:51.170336400Z][com.docker.diagnose.exe][W] (dc1226fa) 2d56ceee-diagnose C<-S NoResponse GET /ping (529.1µs): Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[FAIL] DD0004: is the Docker engine running? Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-05-05T06:19:51.176402300Z][com.docker.diagnose.exe][I] ipc.NewClient: fcc10bca-com.docker.diagnose -> \.\pipe\dockerLifecycleServer VMDockerdAPI
[2023-05-05T06:19:51.176957400Z][com.docker.diagnose.exe][I] (ba2c4a19) fcc10bca-com.docker.diagnose C->S VMDockerdAPI GET /docker
[2023-05-05T06:19:51.176966300Z][com.docker.diagnose.exe][W] (ba2c4a19) fcc10bca-com.docker.diagnose C<-S NoResponse GET /docker (8.9µs): Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-05-05T06:19:51.177573500Z][com.docker.diagnose.exe][I] (ba2c4a19-1) fcc10bca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-05T06:19:51.177573500Z][com.docker.diagnose.exe][W] (ba2c4a19-1) fcc10bca-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-05-05T06:19:52.181037300Z][com.docker.diagnose.exe][I] (ba2c4a19-2) fcc10bca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-05T06:19:52.184053100Z][com.docker.diagnose.exe][W] (ba2c4a19-2) fcc10bca-com.docker.diagnose C<-S NoResponse GET /ping (2.9985ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-05-05T06:19:53.196642300Z][com.docker.diagnose.exe][I] (ba2c4a19-3) fcc10bca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-05T06:19:53.196642300Z][com.docker.diagnose.exe][W] (ba2c4a19-3) fcc10bca-com.docker.diagnose C<-S NoResponse GET /ping (0s): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-05-05T06:19:54.198842700Z][com.docker.diagnose.exe][I] (ba2c4a19-4) fcc10bca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-05T06:19:54.199949700Z][com.docker.diagnose.exe][W] (ba2c4a19-4) fcc10bca-com.docker.diagnose C<-S NoResponse GET /ping (1.107ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-05-05T06:19:55.203131300Z][com.docker.diagnose.exe][I] (ba2c4a19-5) fcc10bca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-05T06:19:55.204370700Z][com.docker.diagnose.exe][W] (ba2c4a19-5) fcc10bca-com.docker.diagnose C<-S NoResponse GET /ping (1.2393ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-05-05T06:19:56.209619600Z][com.docker.diagnose.exe][I] (ba2c4a19-6) fcc10bca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-05T06:19:56.214274700Z][com.docker.diagnose.exe][W] (ba2c4a19-6) fcc10bca-com.docker.diagnose C<-S NoResponse GET /ping (4.6551ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-05-05T06:19:57.217556900Z][com.docker.diagnose.exe][I] (ba2c4a19-7) fcc10bca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-05T06:19:57.218442900Z][com.docker.diagnose.exe][W] (ba2c4a19-7) fcc10bca-com.docker.diagnose C<-S NoResponse GET /ping (886µs): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[2023-05-05T06:19:58.221636400Z][com.docker.diagnose.exe][I] (ba2c4a19-8) fcc10bca-com.docker.diagnose C->S VMDockerdAPI GET /ping
[2023-05-05T06:19:58.223584800Z][com.docker.diagnose.exe][W] (ba2c4a19-8) fcc10bca-com.docker.diagnose C<-S NoResponse GET /ping (1.9484ms): Get "http://ipc/ping": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[PASS] DD0013: is the $PATH ok?
Error response from daemon: open \.\pipe\docker_engine_linux: The system cannot find the file specified.
[FAIL] DD0003: is the Docker CLI working? exit status 1
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0038: is the connection to Docker working?
[FAIL] DD0014: are the backend processes running? 1 error occurred:
* com.docker.vpnkit.exe is not running
[PASS] DD0007: is the backend responding?
[PASS] DD0008: is the native API responding?
[FAIL] DD0009: is the vpnkit API responding? open \.\pipe\dockerVpnKitDiagnostics: The system cannot find the file specified.
[PASS] DD0010: is the Docker API proxy responding?
[SKIP] DD0006: is the Docker Desktop Service responding?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[WARN] DD0011: are the LinuxKit services running? failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
[WARN] DD0004: is the Docker engine running? Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
[PASS] DD0015: are the binary symlinks installed?
[WARN] DD0031: does the Docker API work? error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[WARN] DD0032: do Docker networks overlap with host IPs? error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/networks": open //./pipe/docker_engine_linux: The system cannot find the file specified.
Please note the following 4 warnings:
1 : The check: are the LinuxKit services running?
Produced the following warning: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.
2 : The check: is the Docker engine running?
Produced the following warning: Get "http://ipc/docker": open \.\pipe\dockerLifecycleServer: The system cannot find the file specified.
The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.
3 : The check: does the Docker API work?
Produced the following warning: error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/containers/json": open //./pipe/docker_engine_linux: The system cannot find the file specified.
If the Docker API is not available from the host then Docker Desktop will not work correctly.
4 : The check: do Docker networks overlap with host IPs?
Produced the following warning: error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/v1.24/networks": open //./pipe/docker_engine_linux: The system cannot find the file specified.
If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.
Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address
Please investigate the following 2 issues:
1 : The test: are the backend processes running?
Failed with: 1 error occurred:
* com.docker.vpnkit.exe is not running
Not all of the backend processes are running.
2 : The test: are the LinuxKit services running?
Failed with: failed to ping VM diagnosticsd with error: Get "http://ipc/ping": open \.\pipe\dockerDiagnosticd: The system cannot find the file specified.
The Docker engine runs inside a Linux VM as a service. Therefore the services must have started.
Steps to reproduce the behavior
...
...
The text was updated successfully, but these errors were encountered: