Docker Desktop 4.25.0 WSL Integration is broken on Ubuntu 22.04 LTS #13764
Comments
|
+1, Same problem here |
|
Same problem on WLinux WSL2 |
|
Downgrading to 4.24.2 helps. |
|
Had the same issue. Docker reboot now suddenly has fixed the issue. Docker Version 4.25.0 |
|
@edyu @priisholm @7-zete-7 can you check if reboot fixes the issue? |
|
@bsousaa, reboot does not fixes the issue. And factory reset does not fixes. |
|
Thanks @7-zete-7 can you share a diagnostics id? |
|
@bsousaa, гnfortunately no. I downgrade to 4.24.2 after several reboots and several factory resets because none of this helped and I needed to quickly restore functionality. |
|
I also started experiencing random "docker not found" errors inside of WSL after upgrading to v4.25.0. Especially after not using Docker after some time (no containers running). After some investigation, I suspect that the resource saver function is removing the symlinks inside of WSL when entering into resource saving mode. When the "docker not found" errors start appearing, I simply open the Docker Desktop UI window (which brings Docker back from resource saver mode) and then after a short while the "docker" command inside of WSL starts working again, without restarting anything. Hope this helps finding the culprit. |
Nope. Unfortunately. I rebooted multiple times already. |
I'll try this today. I'm surprised Ubuntu has so many problems as it's the "default" WSL2 setup. |
One additional information. I've enabled systemd and automount on my Ubuntu WSL2 using |
It doesn't work for me. I've even disabled resource saver. |
Ah then likely a different issue for you than for me. Or perhaps related but triggering differently. I have been paying attention today and I can fully confirm now that, at least for me, every time Docker Desktop enters into resource saving mode, the "docker" command is removed from my WSL environment. When I go to the Docker Desktop UI and awaken Docker to get out of resource saving mode, the "docker" command is restored in WSL without restarting anything. This did not happen in previous versions of Docker Desktop (<v4.25.0) where the "docker" command was always available and triggered the resource saver mode to be deactivate when active. EDIT: I can also confirm now that the same happens in another Windows 10 machine I have with Docker Desktop v4.25.0. |
|
I can verify that @7-zete-7 is correct! Docker Desktop 4.24.2 works but 4.25.0 doesn't. |
It didn't. Tried multiple tweaks in configuration and reboots, but unfortunately none of them fixed the problem, so I had to downgrade to get work done. |
edyu
changed the title
I suggest downgrading Docker Desktop 4.25.0 to 4.24.2 |
Yes, I did that and it works fine now, thank you. Btw, I originally installed DD, upgraded to v. 4.25, uninstalled and reinstalled v. 4.24.2 using Chocolatey w.o. any hassles, except for time wasted. |
|
I had the same problem and solved it by downgrading to 4.24.2. |
|
Seems like symlinks broken after upgrading to 4.25. After I manually linked these, I cannot use plugins including buildx or compose. |
|
Some more weird behavior I have found: I can start individual containers via docker desktop UI. And also as many mentioned before |
|
same problem, but with debian WSL too. |
|
Same issue with debian. Tried to fix the symlinks but then compose is not working. |
|
The only thing that worked, was downgrading to the previous version 4.24.2 😐 |
|
Same problem here - burned up two hours this morning trying to fix this. |
I reinstalled v4.24.2, turned on WSL2 integration for Arch only. It immediately fixed the issue, here's the logs from the Something is very wrong with v4.25.0 |
|
I am using the build from this thread with Ubuntu. Though installing this build didn't do a thing for me, changing login shell from fish to bash solves the issue for me. Maybe docker integration doesn't work correctly with fish? I'm not sure whether changing login shell will work on 4.25 without modifications as I already installed the provided build prior to going back to bash. |
Hey! Yeah that's right. We should have a test build ready with a fix for you all to try out a bit later today. |
I'm not even sure anymore that I got it working with any 4.25.0 release. I can't afford more downtime so I downgraded. Hopefully you have enough diagnostics from the others that have responded. |
|
@parberge The diagnostics gathered from everyone on this thread have been very useful and much appreciated. 🙂 I'll post a link to the new build shortly. |
|
👋 Hello, This build should address the issues with integration services. 🤞 https://desktop-stage.docker.com/win/main/amd64/127466/Docker%20Desktop%20Installer.exe |
|
@chelnak can confirm that this build solved this issue for me (WSL2, Ubuntu 20.04, fish-shell). thanks 👍 |
Tested and it works. 🎉 WSL2 Ubuntu 20.04, Windows 10, shell: fish |
|
I was experiencing the same/a similar issue, can confirm that updated build resolved my problem. |
Yes worked for me as well 👍 |
|
same for me, when my docker desktop v4.25.0 is in resource saver mode I cannot execute the "docker" command on WSL terminal |
|
Hey @carlosrmendes , Check out the build here 😀: |
|
We've released a new version of Docker Desktop containing a fix for this issue, you can see the release notes! I'll close this issue for now, but if the issue persists, feel free to open a new issue! |
|
I updated to the latest docker version 4.25.1 and still got this issue... I always have to restart Docker... |
|
same for me, still got the issue @chelnak |
|
Still got the issue in 4.25.1 |
|
Thanks for the updates everyone! Sorry to hear that it's still not working as expected. Would you be able to send over some diagnostics? |
@chelnak it's exactly the same issue as before |
|
v4.26.1 on Win11 - same experience |
|
@Hades32 can you send us a diagnostic and post the id here? Also, are you using fish as your shell? |
|
v4.26.1 on Win11 - still can't run contianers from inside WSL How do I provide diags? |
|
Hey @cipriantarta You can follow the steps here to submit them either via the terminal or via the Docker Desktop UI. https://docs.docker.com/desktop/troubleshoot/overview/#diagnose You'll get an ID once the collection is complete and you can post it here. |
|
@chelnak , this is my diags ID: 457C995C-4680-4CB4-AAB8-716FA2A90DCE/20240110064047 |
|
@cipriantarta Thanks for sending those over. It's a strange one, the issue does look similar. My theory is that you have an old integration agent running that for some reason did not get properly updated. I see no obvious indications as to why that would have happened in the logs though. Would you be able to try the following and let us know the results? Disable/Re-Enable WSL integration
If the result is still the same, then try Reset to factory defaults
Note on the above - You might want to back up your settings.json before you factory reset. Copy-Item -Path $ENV:APPDATA\Docker\settings.json -Destination $HOME\settings.json |
|
So none of that worked. I even uninstalled docker-desktop completely. This is very strange. I might need to upgrade my Ubuntu WSL, but don't have time to deal with that any time soon. I did remember when you said that I have an old agent running, that I have actually exported/imported by WSL image from after a fresh Windows install some very long time ago. Not sure if that's the issue, but it is very strange if it is :) Everything was running smoothly tho before 4.25. Edit:
❯ ls -alh $(which docker)
lrwxrwxrwx 1 root root 48 Jan 8 10:01 /usr/bin/docker -> /mnt/wsl/docker-desktop/cli-tools/usr/bin/docker*
I wonder how does the docker binary get injected in my Ubuntu distro if WSL integration is disabled. Thoughts? So now I have this: ❯ ls -alh $(which docker)
lrwxrwxrwx 1 root root 48 Jan 11 18:57 /usr/bin/docker -> /mnt/wsl/docker-desktop/cli-tools/usr/bin/docker*Ubuntu: ❯ ls -alh $(which docker)
lrwxrwxrwx 1 root root 48 Jan 8 10:01 /usr/bin/docker -> /mnt/wsl/docker-desktop/cli-tools/usr/bin/docker*Looking at the modified date we have Jan 8 & Jan 11, what's going on? Edit 2: I just removed the simlinks from Ubuntu, restarted WSL and now it works |
and others
Description
I have the latest WSL2 (2.0.6.0) and the latest Ubuntu 22.04.3 LTS (which is my default distro) and I also have an Alpine Linux WSL distro as well. I have 2 machines with same setups.
I installed Docker Desktop on both machines and enabled WSL2 Integration. I have checked
Enable Integration with my default WSL distroand alsoEnable integration with additional distroswith both Ubuntu and Alpine enabled.In both cases, I was able to run
docker infoon Alpine.However for Ubuntu 22.04, I have different problems:
Reproduce
dockerin the Ubuntu WSLExpected behavior
docker should connect to Docker Desktop on Windows and no errors
docker version
Client: Cloud integration: v1.0.35+desktop.5 Version: 24.0.6 API version: 1.43 Go version: go1.20.7 Git commit: ed223bc Built: Mon Sep 4 12:32:48 2023 OS/Arch: windows/amd64 Context: default Server: Docker Desktop 4.25.0 (126437) Engine: Version: 24.0.6 API version: 1.43 (minimum version 1.12) Go version: go1.20.7 Git commit: 1a79695 Built: Mon Sep 4 12:32:16 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.22 GitCommit: 8165feabfdfe38c65b599c4993d227328c231fca runc: Version: 1.1.8 GitCommit: v1.1.8-0-g82f18fe docker-init: Version: 0.19.0 GitCommit: de40ad0docker info
Diagnostics ID
D15F1CD0-0E1E-4BE1-AC26-A8242136C3D6/20231027050450
Additional Info
No response
The text was updated successfully, but these errors were encountered: