Open mmj579 opened 1 year ago
it must be the memory leak issue that has been reported over several years and has been fixed in the latest experimental batch of WSL.
Problem: build hangs Reason: Memory usage too high, it crashes the docker engine. Why memory usage high ? Due to WSL not reclaiming ram from docker, and docker not reclaiming its own cache ram Solution: Download the experimental wsl build 1.37 and put this on your .wslconfig
[experimental] autoMemoryReclaim=true
If you want even less memory usage, install docker directly inside WSL as WSL now uses systemd.
There is only issue I've found so far but it doesnt bother me. The auto reclaim feature takes some time to work.
I am having this same exact problem. What is the current status of this ticket? Any updates since June 2023? Below is the docker log file. I am using the latest version 4.24.2. I am using Windows containers.
Description
For unknown reasons
docker build
has stop to work on my Windows 10 development machine. It works fine on other machines.Reproduce
Result: Nothing. No output. The command hangs. Nothing happens at all (probably infinitely - I typically kill the process after 20 minutes or so).
Example:
(The underscore represents the blinking cursor.)
Expected behavior
Messages about the build process and it's completion. Or at least one or more error messages.
NOTE: This works fine on Linux VMs I used as a reference to compare this behavior with.
docker version
docker info
Diagnostics ID
21483797-3CAD-4BD9-8275-0CE2B201645A/20230629081847
Additional Info
I run into the problem three days ago. Then I updated Windows and updated Docker for Windows, restarted my machine. Then everything worked fine. Until the next day: Same situation.
docker build
hang again. This time there's nothing to update. And reboots did not change the situation.