-
Notifications
You must be signed in to change notification settings - Fork 833
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's "resource saver mode" causes WSL to "lock" when AutoMemoryReclaim is set to gradual #11066
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:
|
I also see this with Ansible commands, even |
I am also seeing this. I got the hunch that anything accessing the network also hangs, not just what's accessing the file system. |
I am facing the same issue. Maybe related to #10378 |
same issue here. it's actually just slowing down the system a lot but not hanging indefinitely. one can see this if you ran "service --status-all". it takes minutes to list services one by one. if i stop docker desktop, then the command finishes quickly. |
My problem is similar but not identical. I am running WSL2 Ubuntu 22.04. I can run To fix it, all I have to do is click on the Resume button in Docker Desktop. Then Note that I also confirmed that I do have
I also just updated Docker Desktop today, and the problem persists with Docker Desktop 4.33.1 (161083)
|
Windows Version
Microsoft Windows [Version 10.0.22621.3007]
WSL Version
2.0.14.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.133.1-1
Distro Version
Ubuntu 22.04
Other Software
Docker Desktop 4.26.1 (131620) - Windows version
Repro Steps
When Docker Desktop is running but is in "Resource Saver" mode, running any command that has to read from the disk will "hang" until I manually "wake up" Docker from its Resource Saver mode (by running a container for example).
I'm not really sure about the "read from disk" part, but it's been the common denominator of commands affected by this (e.g.
apt
,ls
,lsof
are all affected, while zsh scripts that are already running ortop/htop
aren't).This issue happens when Docker Desktop is running in resource saver mode AND WSL's autoMemoryReclaim is set to gradual.
I've tried the following scenarios and they don't seem to cause the issue:
autoMemoryReclaim
is set todropcache
autoMemoryReclaim
is disabled (commented out in.wslconfig
)For now I have
autoMemoryReclaim
set todropcache
, but if you want me to run additional tests or need some other info let me know.Expected Behavior
Expected the normal command behavior.
Actual Behavior
I've taken a screen recording while the issue happens:
20240123_204049_explorer.mp4
Diagnostic Logs
Those are the corresponding WSL logs for the screen recording:
WslLogs-AutoMemReclaim-Gradual-2024-01-23_20-40-10.zip
The text was updated successfully, but these errors were encountered: