Docker engine hangs every 7 days like clockwork in Docker Desktop

Docker Desktop
1

Hi,

I’m having a similar issue on Docker Desktop for Windows but every attempt to create a new topic on this forum fails, and docker support won’t help me. Can’t find another entry for this issue.

Docker engine hangs every 7 days like clockwork after I had to reinstall it as it got corrupted and deleted my containers and volumes. I have tried updating to the latest version but the issue persists across several versions. I just get a bunch of unknown errors, troubleshooter is no help, can’t restart or quit docker desktop, the only way to restart is to kill the process in task manager. What could be causing this? I have screenshots, text output from docker diagnose and an ID but don’t know what to do with it.

Thanks

2

I moved your question to a new topic since the other one was about a different issue with Docker CE, not Docker Desktop.

I will contact you in PM to figure out why.

Regarding your issue with Docker Desktop, I’m not sure why it happens, but you should not use Docker desktop as a production server. It was made for development, so the developers likely never tested it for a week. On Windows, using the WSL2 backend it also means the issue could also be caused by WSL2. I don’t know if it should work for a week or not. I only used it temporarily when I needed Linux on Windows desktop.

Well, then please, share them

I had this issue once on Windows, but that was a test release. I never found out why it happened.

If you mean you have screenshots of the output of the diagnose tool, it would be better if you could run the tool again and copy the output as text and share here using code blocks. Help is here: How to format your forum posts

Screenshots of texts are often ignored here as it is hard to read and impossible to quote parts of it. not to mention that as a new user, you could share only two pictures in a post.

We can’t do anything with the ID here as community members so if you want the developers to see it, you will need to share the issue on GitHub

I’m not sure what they would say about running Docker Desktop for a week though. For now, it is enough if you share more details here.

1 Like
3

@rimelek thanks so much for your responses so far. I will try again shortly to recreate the new topic error. I have had no issues with Docker Desktop for Windows in production running WSL2 for the past two years. The unexpected error has me foxed as I can’t identify what’s wrong. I cannot attach any files as I’m a new user. I have the output as text however. Nothing else has changed on the PC. I’d rather not have to reinstall the whole thing again, as only did that a month ago!

Cheers

4

Output from Docker Diagnostic

[PASS] DD0027: is there available disk space on the host?
[SKIP] DD0028: is there available VM disk space?
[SKIP] DD0002: does the bootloader have virtualization enabled?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[SKIP] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[SKIP] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0004: is the Docker engine running? error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Head "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/_ping": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[PASS] DD0015: are the binary symlinks installed?
[FAIL] DD0031: does the Docker API work? prereq failed: is the Docker engine running?
[PASS] DD0013: is the $PATH ok?
[FAIL] DD0003: is the Docker CLI working? prereq failed: is the Docker engine running?
[PASS] DD0005: is the user in the docker-users group?
[FAIL] DD0037: is the connection to Docker working? prereq failed: is the Docker engine running?
[FAIL] DD0014: are the backend processes running? com.docker.backend.exe is not running
[FAIL] DD0007: is the backend responding? prereq failed: are the backend processes running?
[FAIL] DD0010: is the Docker API proxy responding? prereq failed: are the backend processes running?
[SKIP] DD0006: is the Docker Desktop Service responding?
[FAIL] DD0030: is the image access management authorized? prereq failed: is the Docker engine running?
[PASS] DD0033: does the host have Internet access?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0022: is the Virtual Machine Platform Windows Feature enabled?
[PASS] DD0021: is the WSL 2 Windows Feature enabled?
[PASS] DD0024: is WSL installed?
[PASS] DD0025: are WSL distros installed?
[PASS] DD0026: is the WSL LxssManager service running?
[PASS] DD0029: is the WSL 2 Linux filesystem corrupt?
[PASS] DD0035: is the VM time synchronized?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[WARN] DD0004: is the Docker engine running? error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Head "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/_ping": open //./pipe/docker_engine_linux: The system cannot find the file specified.
[PASS] DD0015: are the binary symlinks installed?
[WARN] DD0031: does the Docker API work? prereq failed: is the Docker engine running?
[WARN] DD0032: do Docker networks overlap with host IPs? prereq failed: does the Docker API work?

Please note the following 3 warnings:

1 : The check: is the Docker engine running?
Produced the following warning: error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Head "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/_ping": open //./pipe/docker_engine_linux: The system cannot find the file specified.

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

2 : The check: does the Docker API work?
Produced the following warning: prereq failed: is the Docker engine running?

If the Docker API is not available from the host then Docker Desktop will not work correctly.

3 : The check: do Docker networks overlap with host IPs?
Produced the following warning: prereq failed: does the Docker API work?

If the subnet used by a Docker network overlaps with an IP used by the host, then containers
won't be able to contact the overlapping IP addresses.

Try configuring the IP address range used by networks: in your docker-compose.yml.
See https://docs.docker.com/compose/compose-file/compose-file-v2/#ipv4_address-ipv6_address

Please investigate the following 2 issues:

1 : The test: is the Docker engine running?
Failed with: error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Head "http://%2F%2F.%2Fpipe%2Fdocker_engine_linux/_ping": open //./pipe/docker_engine_linux: The system cannot find the file specified.

The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.

2 : The test: are the backend processes running?
Failed with: com.docker.backend.exe is not running

Not all of the backend processes are running.

5

I’m going to fix it for you only this time.

Done. I think I did a terrible job since only you know what the actual output was and what was your note…

6

I read the error messages. but all I can say is that you can try to open an issue on GitHub (linked in my first post)

Since you could run Docker Desktop and it stopped later, it cannot be permission issue. People reported before that WSL used too much resources when running for long. It was usually reported by Docker Desktop users, but I think it was a WSL issue. Or maybe you run something every week, or Windows runs something weekly that stops Docker Desktop. These are my guesses, but the developers on GitHub could have other ideas.

7

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.