Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker stopped working in WSL 2.3.11.0 #12033

Closed
craigloewen-msft opened this issue Sep 13, 2024 · 1 comment
Closed

Docker stopped working in WSL 2.3.11.0 #12033

craigloewen-msft opened this issue Sep 13, 2024 · 1 comment

Comments

@craigloewen-msft
Copy link
Member

Windows Version
Microsoft Windows [Version 10.0.22635.3930]

WSL Version
2.3.11.0

Are you using WSL 1 or WSL 2?

WSL 2

WSL 1
Kernel Version
6.6.36.3-microsoft-standard-WSL2

Distro Version
Ubuntu 20.04

Other Software
Docker version 27.0.3, build 7d4bcd8

Repro Steps
Update WSL via windows store
Launch Docker
Expected Behavior
Docker to launch successfully

Actual Behavior
Docker fails to launch

Diagnostic Logs
No response

Some additional context
This morning WSL was updated via the Windows store, after that Docker failed to launch with a generic "exit code 1" error message. I uninstalled and reinstalled Docker and then it still failed to launch complaining it couldn't get the disk size.

I've seen some other issues related to Docker #11742 and #11771 and kernel version 6.6.36.3, but those don't seem to apply to me since I'm not building the kernel my self (installing from Microsoft Store), and I don't have "kernel=" in my .wslconfig.

Also, installing Docker using Hyper-V instead of WSL has no problems.

Copy link

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 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, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] 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!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant