github-actions[bot]
commented
2 months ago Logs are required for review from WSL team
If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'. Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.
How to collect WSL logs
Download and execute [collect-wsl-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-wsl-logs.ps1) in an **administrative powershell prompt**: ``` Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1 Set-ExecutionPolicy Bypass -Scope Process -Force .\collect-wsl-logs.ps1 ``` The script will output the path of the log file once done. If this is a networking issue, please use [collect-networking-logs.ps1](https://github.com/Microsoft/WSL/blob/master/diagnostics/collect-networking-logs.ps1), following the instructions [here](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#collect-wsl-logs-for-networking-issues) Once completed please upload the output files to this Github issue. [Click here for more info on logging](https://github.com/microsoft/WSL/blob/master/CONTRIBUTING.md#8-collect-wsl-logs-recommended-method) If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.View similar issues
Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!
Open similar issues:
- CRITICAL DEADLY BUG: WSL2/VSCODE/Docker Desktop Memory Leak clobbers WSL /home/username/* ALL files Suddenly Disappear! (#9728), similarity score: 0.73
- error code 0x8007274c (#10174), similarity score: 0.72
Closed similar issues:
- WSL2 randomly crashes (#7368), similarity score: 0.74
- Docker Desktop and Docker in general crashing and hanging. Errors wont go away even after full wipe (#9974), similarity score: 0.73
- How can I troubleshoot intermittent WSL2 system shutdown? (#11251), similarity score: 0.72
Note: You can give me feedback by thumbs upping or thumbs downing this comment.
SledgeHammer01
Windows Version
Microsoft Windows [Version 10.0.22631.4037]
WSL Version
2.2.4.0
Are you using WSL 1 or WSL 2?
Kernel Version
5.15.153.1-2
Distro Version
No response
Other Software
Docker Desktop 4.33.1 with Kubernetes enabled
Repro Steps
Expected Behavior
That I can shutdown Docker and my PC without the docker data volume becoming corrupted
Actual Behavior
Docker data volume becomes corrupt after 2 - 3 exits of Docker
Diagnostic Logs
I am unable to provide diagnostic logs since when Docker w/ Kubernetes data volume becomes corrupt, it is unusable and you have to start from scratch. Some errors:
error spotted in wslbootstrap log: "[2024-08-04T13:04:00.245585549Z][wsl-bootstrap][F] preparing block device /dev/sdd: mounting disk: input/output error"
running engine: waiting for the VM setup to be ready: starting WSL engine: bootstrapping in the main distro: starting wsl-bootstrap: context canceled
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"
running wsl-keepalive in "docker-desktop-data": WSL engine terminated abruptly
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.