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 Desktop fails to start up after fresh install. com.docker.backend keeps crashing #13027

Closed
katomilis opened this issue Oct 23, 2022 · 6 comments

Comments

@katomilis
Copy link

  • [ X] I have tried with the latest version of Docker Desktop
  • [ X] I have tried disabling enabled experimental features
  • [ X] I have uploaded Diagnostics
  • Diagnostics ID:
    diagnose.txt
    log.txt

Actual behavior

Docker Desktop remains invisible, keeps starting up crashed backend service.

Expected behavior

Docker Desktop starts up

Information

I just installed Docker Desktop for the first time. Tried version 4.13, 4.12 and 4.11.1.
These are the logs of 4.11.1.
I reinstalled Docker Desktop multiple times and rebooted in between installs.

  • Windows Version: Windows 10 Home
  • Docker Desktop Version: 4.11.1
  • WSL2 or Hyper-V backend? WSL2
  • Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check

diagnose.txt

@mklueh
Copy link

mklueh commented Oct 23, 2022

Same here. Reboot did not help

@viceice
Copy link

viceice commented Oct 24, 2022

@jweslley
Copy link

It seems the solution for now is reinstalling. It worked for me but I lost all images/volumes :/ #13025 (comment)

@MattiasDC
Copy link

It seems the solution for now is reinstalling. It worked for me but I lost all images/volumes :/ #13025 (comment)

Reinstalling didn't work for me

@docker-robott
Copy link
Collaborator

There hasn't been any activity on this issue for a long time.
If the problem is still relevant, mark the issue as fresh with a /remove-lifecycle stale comment.
If not, this issue will be closed in 30 days.

Prevent issues from auto-closing with a /lifecycle frozen comment.

/lifecycle stale

@docker-robott
Copy link
Collaborator

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

/lifecycle locked

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

6 participants