-
Notifications
You must be signed in to change notification settings - Fork 836
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WSL2 and Docker Desktop crashed #10752
Comments
Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! Open similar issues:
Closed similar issues:
You can give me feedback by thumbs upping or thumbs downing this comment. |
Experiencing same problem. I suppose a more precise description would be: After launching a WSL distro, opening another shell like Weird thing is, on my PC, this problem occurs only with a certain distro. I installed Ubuntu and it is not observing this issue so far. EDIT: I'm using Distrod, which appears to be the same with the original issue author here. Could be a Distrod issue. |
Same thing, I also use Arch Linux with Distrod. |
I've found I could avoid the problem by disabling Distrod; i.e. launch the Distrod instance, and |
I think the easiest way to fix this is to do go into wsl once (still works for me after wsl --shutdown) then run This works for me so far, not sure yet if the distrod disablement sticks around after a windows restart. |
I have the same problem with vscode this morning. I have tried above solutions but to no avail. This was simply NOT happening yesterday. Only difference is I am working from the office today. I'll retest from home this afternoon, just in case. Looks like a problem with the filesystem manager here. |
I think that currently is the only solution |
No distrod in my case, so this does not work for me, I'm afraid. |
I am also including the "code -s" I get when I execute vscode as "code ." in any WSL2 folder: CPU % Mem MB PID Process Connection to 'wsl+Ubuntu' could not be established |
My steps to fix this:
You will need to edit the wsl.conf file to ensure systemd starts up on boot. Add these lines to the /etc/wsl.conf (note you will need to run your editor with sudo privileges, e.g: sudo nano /etc/wsl.conf):
Then: Restart your wsl in your terminal, seems good now! |
Thanks @httpete, followed the steps you posted, fixed my issue. |
This does not work for me but anyway VSCode is working correctly if I run it from home. This seems to be a problem only at the office, so I will try and solve it internally with my company's IT. Thanks anyway, guys. |
The suggestion from here works for me. Add the following to .wslconfig:
After rebooting the laptop (just wsl --shutdown was not sufficient for me) I can start VS Code (both from the exe or the wsl terminal) & Docker desktop without issues. Don't know what are the repercussions for disabling virtio9p but things seem to work okay for me. |
Entering WSL and disabling I got into WSL with |
I'm also seeing this. Current workaround is to downgrade to WSL 1.3.17.0. |
UBUNTU 22.04
fixed it for me. |
Thanks to @httpete , problem solved! |
Windows Version
10.0.22631.2715
WSL Version
2.0.9.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
Debian
Other Software
Docker Desktop 4.25.1 (128006)
Repro Steps
another situation:
docker ps
, returnCannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Docker Desktp - Unexpected WSL error
Everything is ok yesterday, I don't known what happened? Maybe Windows updated?
Expected Behavior
Actual Behavior
Diagnostic Logs
No response
The text was updated successfully, but these errors were encountered: