Open SledgeHammer01 opened 4 months ago
After getting the error spotted in wslbootstrap log: "[2024-08-04T13:04:00.245585549Z][wsl-bootstrap][F] preparing block device /dev/sdd: mounting disk: input/output error"
. My Docker is basically corrupt and there is no way to start it and I have to uninstall it and reinstall it and all my k8s stuff.
Tried completely uninstall and downgrading to 4.29.0 since I don't recall having this issue until more recently. This version doesn't reliably start up K8s on a reboot. Get's stuck at "starting Kubernetes" and I have to restart docker a bunch of times.
Another error:
running engine: waiting for the VM setup to be ready: starting WSL engine: bootstrapping in the main distro: starting wsl-bootstrap: context canceled
After installing just ONE application via Helm, Docker is once again hosed and requires a complete uninstall and reinstall.
Yet another error:
error spotted in wslbootstrap log: "[2024-08-04T14:00:49.850833298Z][wsl-bootstrap][F] open /mnt/host/wsl/docker-desktop-data/isocache/entries/docker-wsl-cli.iso/643b529b8b4a6c7b1f239a83cd50e615b703ffea21034698ff60fe88bc5b5957: read-only file system"
And another:
running wsl-keepalive in "docker-desktop-data": WSL engine terminated abruptly
4th error of the day:
deploying WSL2 distributions ensuring main distro is deployed: checking if main distro is up to date: checking main distro bootstrap version: getting main distro bootstrap version: open \wsl$\docker-desktop\etc\wsl_bootstrap_version: The network name cannot be found. checking if isocache exists: CreateFile \wsl$\docker-desktop-data\isocache\: The network name cannot be found.
FYI: SFC and DISM scans pass 100%. BIOS and microcode fully up to date. No overclocking. Memtests all pass with flying colors. 0 problems with the system otherwise.
Completely uninstalled WSL, HyperV, Containers, all WSL distros, data directories, etc. Reinstalled docker + K8s, installed ONE application via Helm and immediately got "Structure needs cleaning".
I have also been getting problems with the new docker version. When iu run an AI workload in a container. This wasnt happening until I updated. Im not sure which version introduced it.
@lorenrh any update on this? It's completely unusable when it corrupts the data once or twice a DAY
4.34.2 had a crash with "running wsl-keepalive in "docker-desktop-data": WSL engine terminated abruptly" too Diagnostic ID: F5FC5563-1C07-4889-9998-5D2A7F63F50A/20241005000149
Description
My Kubernetes instance has the following installed:
Often times, when I start up Docker, I get various WSL errors
When I tried to collect diagnostics while it was in a "hosed" state, it ended with:
I don't know how useful it will be though since when it's in a "hosed" state, the docker daemon is crashed and it can't connect to it.
EDIT: Yes, I am cleanly shutting down Docker before rebooting.
Reproduce
Starting docker desktop
Expected behavior
No response
docker version
docker info
Diagnostics ID
N/A
Additional Info
No response