Question
When running containers under WSL2 on Windows, the C: drive eventually runs out of disk space because dump files are continuously generated and accumulated in the [wsl-crashes] directory.
The file named [wsl-crash-1789395552-84-_opt_drawio_drawio-11.dmp] grows to approximately 160 GB within about 10 minutes. It continues to grow until all available space on the C: drive is exhausted.
In my environment, the file grew to approximately 700 GB before the C: drive ran out of free space.
This file is not generated when running other Docker containers, or, if it is generated, its size is only a few KB.
Is there a way to prevent this dump file from being generated, or to limit its size or otherwise prevent it from growing excessively?
・Windows10 Home 22H2(Bilud: 19045.7725)
・WSL Ver: 2.7.14.0
・Docker Ver: 29.6.2(Build: dfc4efb)
・Docker Desktop Ver: 4.91.0(239619)
Context
No response
Question
When running containers under WSL2 on Windows, the C: drive eventually runs out of disk space because dump files are continuously generated and accumulated in the
[wsl-crashes]directory.The file named
[wsl-crash-1789395552-84-_opt_drawio_drawio-11.dmp]grows to approximately 160 GB within about 10 minutes. It continues to grow until all available space on the C: drive is exhausted.In my environment, the file grew to approximately 700 GB before the C: drive ran out of free space.
This file is not generated when running other Docker containers, or, if it is generated, its size is only a few KB.
Is there a way to prevent this dump file from being generated, or to limit its size or otherwise prevent it from growing excessively?
・Windows10 Home 22H2(Bilud: 19045.7725)
・WSL Ver: 2.7.14.0
・Docker Ver: 29.6.2(Build: dfc4efb)
・Docker Desktop Ver: 4.91.0(239619)
Context
No response