-
Notifications
You must be signed in to change notification settings - Fork 287
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
Docker Desktop 2.3.5.0 on Windows 2019[0|7] WSL2 isn't working #8183
Comments
Same issue here, rolling back to |
Same here, Diagnostics ID |
Same issue here. Diagnostics ID: DB6939B5-5158-41B4-8EA0-9DC8A82F5590/20200822225510 |
Ditto :/ Diagnostics ID: D4026442-6C7E-4057-AF76-92429D865C0D/20200823000954 [edit] - can confirm rolling back to 2.3.0.4 restores WSL2 functionality |
same after putting: $env:COMPOSE_CONVERT_WINDOWS_PATHS=0 into my powershell, |
Thanks for reporting the issue, we are aware of the issue, and working on a fix. |
Can you check if this private build: https://desktop-stage.docker.com/win/edge/47392/Docker%20Desktop%20Installer.exe fixes the issue ? |
Didn't fix the issue for me, still running into the same errors |
@simonferquel for me is Docker from WSL2 working again after I installed private build 👍 |
The private build completely breaks everything for me.
|
I just started seeing this issue after updating to the latest windows insider preview build in the dev channel. Here is my build information:
The following Docker Desktop versions have failed for me:
Diagonstic ID: E7D67F4B-3FB7-40D2-A9E2-2F86C881F363/20200824192758 Finally the error:
|
I have the same issue. Installing the private build mentioned above made no difference on my machine. Still works fine from windows but Docker commands from WSL fails with
I'm on Windows 1909 (which just got WSL 2 support) and WSL Fedoraremix. |
+1, apparently, according to the other issues, the problem persists even when downgrading to the previous Docker for Desktop version. |
I should note, Docker Desktop is working for me in my Ubuntu WSL2 installation, but not in my Arch installation. The error message I posted above is from when I try to start the distro proxy for Arch. I don't know where the source code is for the distro proxy, but it looks like it is failing looking up the users group. I think its failing in the WSL2 side as I see calls to |
I ran into the same problem and found integration with my WSL distros disabled though I hadn't disabled it. After I re-enable the integration, |
@kenXengineering is the Arch installation marked as your default WSL distro? Because @ad-on-is has this issue with Ubuntu being the default distro: #8208 |
I tried changing my default distro, from Ubuntu to Kali, but it had no effect. WSL in Ubuntu still didn't work. As @grthr mentioned, it works with the latest stable of Docker Desktop. |
Worked for me. |
For wsl archlinux, reverting |
Did not work for me. Stable 2.3.0.4 worked for me. |
@grthr yes, Arch is marked as my default WSL distro. I'm also going to try reverting |
So I was able to revert |
The Docker Desktop 2.3.5.1 update just rolled out which I thought would fix this. I still had the same problem with my default distro FedoraRemix after the update, but I was able to install another WSL distro (Ubuntu) and use Docker from there. |
I installed the update, went into settings and disabled WSL integration, then re-enabled it after restarting and it worked.
|
2.3.5.1 still doesn't work with |
Edit: After closing + opening a new WSL 2 terminal/session, it works now with (edge) release Installed the update, now I get the |
Hi, Same error, I cant work :
The 2.3.5.1 didnt fix it. DIAGNOSTIC ID : A7C77B7B-5902-4102-883F-48D39E442649/20200826082556 |
@xzile it seems you have created many containers previously with the broken mounts in 2.3.5.0 or 2.3.5.1... If you have a way to re-create them, can you remove them from windows (using |
@simonferquel: The docker socket file ( |
Rolled back to 2.3.4.0 and rebuilt to get things going again. Will attempt a rebuild sometime later. Thanks for the diligence. |
Not sure what's going on but after today updates:
Docker
Downgrading |
Yes, downgrading to Docker for Desktop Edge |
Hi there, sorry for the last few edge releases: we tried to fix an issue with mounts and WSL2 preventing people to do things like |
@simonferquel still have problem in this private build .
looks like the I.E. i use wslArch and my glibc's version is |
Originally had problems but it may have been computer-related and required a restart. Uninstalled 2.3.4.0 and installed the private build, and things seem to be working fine for me. Can't attest to the upgrade process due to the uninstall that occurred. |
The mounts fix has been released in the latest edge 2.3.6.1. Please give it a try if you can and let us know how it goes! |
Edit: For me, with the latest Docker for Desktop (Edge) release |
and sadlly i find the |
We have a fix inbound for glibc update. Not sure when it will be out though. |
@simonferquel thanks! i can wait for it. |
For me updating to edge 2.3.6.1, which was supposed to fix this, did the opposite and caused it! |
The version 2.3.6.1 didnt fix it. I appreciate your efforts. Diagnostic ID : A7C77B7B-5902-4102-883F-48D39E442649/20200909085648 |
I don't really understand why is this closed, the issue still exist on ArchWSL with 2.32-4. @simonferquel Do we have an other issue to follow related to glibc update? |
@smallst Seems similar, but my WSL instance didn't die just throw the segmentation violation errors. |
@ncsibra the original issue (as seen trough the logs) was not about glibc issue, but about a bind mount issue that we fixed. |
The fix for the glibc issue has been released in stable 2.4.0.0. |
2.4.0.0 just introduced this issue for me (using ubuntu 18.04, WSL2). Diagnostic ID: 6F8FDD6C-C27C-43B2-980F-D5D770523DB6/20200930160344. Do I need to open a new issue? |
@realmgic can you stop docker desktop, remove |
@simonferquel - I didn't go with that route (removing /var/lib/docker-desktop/mounts.data would remove the mounts to containers I use, right?). Here what fixed it for me:
Before:
After:
Not sure why some things used to be directories are now a file, also - the permission used to be root:root, but it's now my own user so I don't know what's up with that. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
Closed issues are locked after 30 days of inactivity. If you have found a problem that seems similar to this, please open a new issue. Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. |
E4FA4851-345B-4CBC-983F-A0642A2AE91B/20200821210929
E4FA4851-345B-4CBC-983F-A0642A2AE91B/20200821212110
Expected vs Actual behavior
I upgraded to the latest Edge release. Docker on the Windows side is fine (cmd/powershell). WSL2 doesn't work anymore.
Information
Something clearly is in a restart loop.
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: