Open iambiao opened 6 months ago
I have this happen consistently. I'm mostly wondering if someone has input on how to diagnose further?
I'm running Immich and Portainer if that's relevant. Windows and WSL are fully up to date.
My problem has been resolved. The reason is that my laptop is running low on memory. I stopped some unnecessary programs and released some memory, but this error did not occur. You can check the resource status of the system
Description
windows 11 professional 23H2 OS build number 22631.3447 D:\docker>docker --version Docker version 26.0.0, build 2ae903e
D:\docker>wsl --version WSL version: 2.1.5.0 kernel version: 5.15.146.1-2 WSLg version: 1.0.60 MSRDC version: 1.2.5105 Direct3D version: 1.611.1-81528511 DXCore version: 10.0.25131.1002-220531-1700.rs-onecore-base2-hyp Windows version: 10.0.22631.3447
After the Docker starts, I use D: \ Docker>Docker build - t yolov8_cpu Create a Docker image and after running for 20 minutes, an error window will pop up with the following message:
Docker Desktop - WSL distro terminated abruptly A WSL distro that Docker Desktop relies on has exited unexpectedly. This usually happens as a result of an external entity terminating WSL (e.g. running wsl --shutdown). Restart Docker Desktop. If the issue persists, collect diagnostics and submit an issue. running wsl-keepalive in "docker-desktop-data": WSL engine terminated abruptly I need to choose to exit or restart, and then the build session exits。
Attempted unsuccessful methods: ● Turn WSL2 on or off during installation ● Restart after uninstallation, restart after installation, and then open again ● Netsh Winsock reset, restart LSP repair tool ● Exit Proximitor, 360 VPN Exit Docker, execute the following command, and then open again Wsl -- unregister ranger desktop Wsl -- unregister ranger desktop data ●Delete C:/users/. Docker, restart
how can i do next step,need help please.thanks
Reproduce
Docker build - t yolov8_cpu
Expected behavior
No response
docker version
docker info
Diagnostics ID
1339
Additional Info
No response