Possible memory leak in WSL2 backend

[Yashar8991]

• [x] I have tried with the latest version of Docker Desktop
• [x] I have tried disabling enabled experimental features
• [x] I have uploaded Diagnostics
• Diagnostics ID:8F19DAA1-8265-4E44-8946-8C7E6A360591/20230422152547

Information

• Windows Version:windows 10
• Docker Desktop Version:latest
• WSL2 or Hyper-V backend? Hyper-V
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM:

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

[sam-thibault]

Thank you for uploading diagnostics. Can you please describe the issue you are having?

[Yashar8991]

Why WSL2 consume memory like a wolf

[hexxone]

Same problem. I am sitting at ~15GB of RAM usage without a Single container or Plugin running. The Problem persists even after restarting Docker Desktop. My guess is a severe Memory Leak in the WSL2 Backend... Only option for me is to restart my PC daily.

[Yashar8991]

I deleted f*cking docker. Because this shit destroyed my machine

[samuk190]

Why WSL2 consume memory like a wolf

its not wsl, it is the docker.

[samuk190]

Same problem. I am sitting at ~15GB of RAM usage without a Single container or Plugin running. The Problem persists even after restarting Docker Desktop. My guess is a severe Memory Leak in the WSL2 Backend... Only option for me is to restart my PC daily.

This bug has been around over 3 years, and no expectation to be fixed. I dont even know why people are discusing other stuf rather than this.. Because when docker use all ram the build became slow , and the computer can crash if not set limits on .wslconfig. Everyone that makes issue here, the devs ask same question while they don't even need to because this bug is happening with them, it happens with EVERYONE, just installing windows iso, wsl2 an d docker, it happens the bug. WSL2 released a feature that auto claims memory ram back to host 1 year ago, there is no reason to docker getting all ram and not freeing it.