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

WSL2 Crashing With Docker #12376

Open
1 of 2 tasks
Hashah2311 opened this issue Dec 13, 2024 · 5 comments
Open
1 of 2 tasks

WSL2 Crashing With Docker #12376

Hashah2311 opened this issue Dec 13, 2024 · 5 comments

Comments

@Hashah2311
Copy link

Windows Version

Microsoft Windows [Version 10.0.22635.4580]

WSL Version

2.4.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.167.4-1

Distro Version

Ubuntu

Other Software

Docker Desktop with WSL integration Version 4.37.0
Immich self-hosted container image

Repro Steps

Launch anything on wsl related to docker, such as a container, docker --help, etc.

Expected Behavior

Continuing with the process.

Actual Behavior

WSL crashes with docker showing the error
Docker Desktop WSL Integration Terminated Abruptly.
WSL Error:

[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

Diagnostic Logs

Attaching WSL logs.
WslLogs-2024-12-13_22-50-55.zip

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 13, 2024

Thank you for reporting this @Hashah2311. Looking at the logs, I can see that the issue is that the VM exits with triple fault:

Microsoft.Windows.Lxss.Manager	AbnormalVmExit	12-13-2024 09:24:30.687	"	"	"Details: 
{
	""""Status"""": 	-1070137082
	""""ExitType"""": 	""""UnexpectedExit""""
	""""Attribution"""": 	[{""""SystemExit"""":{""""Detail"""":""""UnexpectedExit"""",""""Initiator"""":""""GuestOS""""}}
	{""""WorkerExit"""": 
	{
		""""Type"""": 	""""StoppedOnReset""""
		""""Detail"""": 	""""TripleFault""""
		""""Initiator"""": 	""""GuestOS""""
	}
	{""""TripleFault"""": 	{""""ErrorType"""":18446744071562068001}}]
}
wslVersion: 	2.4.5.0"				4832	17912	5		00000000-0000-0000-0000-000000000000		

Unfortunately those are usually caused by hardware issues so they're pretty difficult to root cause. Can you run a memory check and see if anything comes out ?

@OneBlue OneBlue added needs-investigation likely actionable and/or needs more investigation needs-author-feedback and removed needs-investigation likely actionable and/or needs more investigation labels Dec 13, 2024
@Hashah2311
Copy link
Author

Hashah2311 commented Dec 14, 2024

@OneBlue I ran memory diagnostics (assuming you meant checking up my RAM) and it shows no errors.

@Hashah2311
Copy link
Author

@OneBlue Can you help me?

@OneBlue
Copy link
Collaborator

OneBlue commented Dec 16, 2024

Interesting. Could you share which CPU model your machine is running on ?

@Hashah2311
Copy link
Author

My machine configuration:
CPU: Intel Core i5-10300H
Ram: 8GB
GPU: NVIDIA GeForce GTX 1650 4GB
OS: Windows 11 Home Insider Preview (Beta)

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

No branches or pull requests

2 participants