for-win
for-win copied to clipboard
docker
Docker container hangs randomly after running normally for several hours
- [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: BE97BD5E-5BC7-4DDA-8E26-5911C29C4522/20230112191850
Actual behavior
Docker containers randomly hang forever after running normally for hours.
More specifically, I can normally start the containers and codes can run normally inside containers at the beginning. At some random time (typically in 8~36 hours after the codes start to run), the codes stop outputting results. If we check the Docker Desktop software at that time, we can find we cannot kill or restart containers, and we have to restart the wsl2 or Docker Desktop.
Expected behavior
Docker containers will not randomly hang.
Information
-
Is it reproducible? Yes, it is 100% reproducible after I observe this phenomenon for about one month. However, this issue appears at some random time in 8~36 hours after the codes start to run.
-
Is the problem new? Yes, it just appeared around one month ago. Before that time, this desktop can run codes inside containers without any problems. Also, another desktop that has very similar hardware and software can still run the same codes normally so far.
-
Did the problem appear with an update? Not with an update. But our IT department re-imaged this desktop and reinstalled the windows 10 system, and then I upgraded this system to windows 11. I am not sure if something is wrong here.
-
Windows Version: Windows 11 Enterprise, 22H2
-
Docker Desktop Version: 4.15.0 (93002)
-
WSL2 or Hyper-V backend? WSL2
-
Are you running inside a virtualized Windows e.g. on a cloud server or a VM: I am running codes with VS Code on the Windows system. The backend is Ubuntu.
Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check
[PASS] DD0027: is there available disk space on the host? [PASS] DD0028: is there available VM disk space? [PASS] DD0002: does the bootloader have virtualization enabled? [SKIP] 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? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0013: is the $PATH ok? [PASS] DD0003: is the Docker CLI working? [PASS] DD0005: is the user in the docker-users group? [PASS] DD0014: are the backend processes running? [PASS] DD0007: is the backend responding? [PASS] DD0008: is the native API responding? [PASS] DD0009: is the vpnkit API responding? [PASS] DD0010: is the Docker API proxy responding? [PASS] DD0006: is the Docker Desktop Service responding? [PASS] DD0012: is the VM networking working? [SKIP] DD0030: is the image access management authorized? [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? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0032: do Docker networks overlap with host IPs? No fatal errors detected.
Steps to reproduce the behavior
- Start the Docker Desktop and VS Code.
- Start the containers.
- Run the python codes inside the container with VS Code.
- After several hours, we can see the codes stop outputting results, and containers start to hang.
Here I added several methods that I tried but still did not work:
- Reinstalling Docker Desktop, Ubuntu, and VS Code (and its docker extensions)
- Rebooting the windows system.
- Deactivate and reactive the wsl2 feature.
- Resetting the Docker Desktop, re-pulling the image, and rebuilding the containers. I am quite sure the image is not the issue because I can use it normally on the cluster and another desktop.
- Uninstalling the anti-virus software.
- Monitoring the memories. There are enough memories.
I also have this issue. I can no longer run my docker containers on windows 11.
Something is messed up with WSL2 on windows 11. I have tried uninstalling and reinstalling WSL to no avail. Very frustrating and not sure this issue is getting the attention it deserves.
@jiayingqi Does the wsl itself hang or just the docker?
There is an issue with WSL, if pc sleeps, then after waking up, WSL itself might hang forever until it's restarted. This should also affect running VSCode instances where the WSL window would complain about not being able to connect to WSL.
@jiayingqi Does the wsl itself hang or just the docker?
There is an issue with WSL, if pc sleeps, then after waking up, WSL itself might hang forever until it's restarted. This should also affect running VSCode instances where the WSL window would complain about not being able to connect to WSL.
I am only sure the docker daemon hangs because I can use wsl --shutdown in Powershell to shut down the docker.
The sleep mode might not be the issue because I set the desktop never to sleep.
I dont think its sleep mode either. I read somewhere that Windows changed the way the WSL is virtualized? Maybe they were using hyperV before and something changed?
Once WSL freezes, I cannot even open a responsive Ubuntu terminal. It is very frustrating as I can no longer run my docker stack.
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
I have the same issue. I'm using docker both on a production environment and a dev environment. The worst is that it freeze after some random time only if I do nothing inside the containers for more than 30 minutes and only with my dev environment.
In the production environment, it works good and never freeze (It's already been up for 2 years now).
So any solution is welcomed.
I'm facing such an issue, where on local compose compilation, a container that is up and has a vite dev server running, it hangs after several hours and then when docker tries to even stop the container it hangs, even Docker Desktop hangs and after stopping/starting, it never finishes loading and it needs a PC restart.
I have now installed Docker Desktop without WSL integration on Hyper-V and I'm running the same containers on Windows Powershell with the same vite dev server running without any issues.
I suspect that this might be a WSL issue.
This all happened after I updated everything, Docker Desktop and WSL itself to the latest version.
I'm facing such an issue, where on local compose compilation, a container that is up and has a vite dev server running, it hangs after several hours and then when docker tries to even stop the container it hangs, even Docker Desktop hangs and after stopping/starting, it never finishes loading and it needs a PC restart.
I have now installed Docker Desktop without WSL integration on Hyper-V and I'm running the same containers on Windows Powershell with the same vite dev server running without any issues.
I suspect that this might be a WSL issue.
This all happened after I updated everything, Docker Desktop and WSL itself to the latest version.
When you have docker hanging up, do the following command in powershell: wsl --shutdown (it completely stops the WSL Virtual Machines)
I'm facing such an issue, where on local compose compilation, a container that is up and has a vite dev server running, it hangs after several hours and then when docker tries to even stop the container it hangs, even Docker Desktop hangs and after stopping/starting, it never finishes loading and it needs a PC restart. I have now installed Docker Desktop without WSL integration on Hyper-V and I'm running the same containers on Windows Powershell with the same vite dev server running without any issues. I suspect that this might be a WSL issue. This all happened after I updated everything, Docker Desktop and WSL itself to the latest version.
When you have docker hanging up, do the following command in powershell:
wsl --shutdown(it completely stops the WSL Virtual Machines)
I'm using wsl --shutdown quite often when WSL hangs on machines with low RAM, but this PC I'm facing the problem has 128GB RAM. When the container hangs, it throws an error on the CLI at the WSL terminal, something like "Failed to stop the container", I run wsl --shutdown in a PowerShell session, It stops the Docker Desktop and the WSL VM together and the WSL restarts after a short while, but the Doskcer Desktop I have to open it manually, I open the UI tool, but it hangs there saying docker desktop is loading while the WSL renders usable but without docker CLI. The remedy to this is to restart the PC.
No issues so far since I changed Docker to use Hyper-V instead of WSL, but I'm running Docker Linux containers throw PowerShell now, not WSL.
I'm facing such an issue, where on local compose compilation, a container that is up and has a vite dev server running, it hangs after several hours and then when docker tries to even stop the container it hangs, even Docker Desktop hangs and after stopping/starting, it never finishes loading and it needs a PC restart.
I have now installed Docker Desktop without WSL integration on Hyper-V and I'm running the same containers on Windows Powershell with the same vite dev server running without any issues.
I suspect that this might be a WSL issue.
This all happened after I updated everything, Docker Desktop and WSL itself to the latest version.
Curiously I'm having the same issue, but using Hyper-V. I have to restart docker to get containers to behave. Here's my comment on another Issue: https://github.com/docker/for-win/issues/12997#issuecomment-1915489953
Having exactly the same issue using Hyper-V. Corresponding diagnostics from the original post for my system are below:
- I have tried with the latest version of Docker Desktop (4.28.0)
- I have disabled enabled experimental features
- I have disabled Resource Saver
Actual behavior Docker containers randomly hang forever after being inactive for a random amount of time.
More specifically, I can normally start the containers and they can run normally to start. At some random time having been left idle for a period of time (between 1 & 4 hours) the containers become unresponsive when I try to access. If we check the Docker Desktop software at that time, we can find we cannot kill or restart containers, and we have to restart Docker Desktop.
All applications that access the Docker Desktop API (e.g. to connect to terminals/run exec etc.) just hang, and Docker Desktop cannot make any changes to containers - however some containers can still be connected to and a terminal session opened and are responsive, others have 'unable to load the terminal, HTTP code 400 unexpected - exec process not started.
Curiously enough - while collecting this info, some containers have started to respond (after 30mins) - whereas others still haven't.
A 'Restart Docker Desktop' resolves the issue though (until it occurs later) Expected behavior Docker containers will not randomly hang.
Information Is it reproducible? Happens one-two times/day
Is the problem new? Yes, it just appeared around one month ago.
Did the problem appear with an update? No
Windows Version: Windows 11 Enterprise, 22H2
Docker Desktop Version: 4.28.0
WSL2 or Hyper-V backend? HyperV
Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No. Windows on bare-metal.
Output of & "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check Starting diagnostics
[2024-03-22T16:16:42.670484800Z][com.docker.diagnose.exe.ipc][I] ipc.NewClient: ce4233a5-diagnose -> \.\pipe\dockerBackendApiServer BackendAPI [2024-03-22T16:16:42.674238600Z][com.docker.diagnose.exe.ipc][I] (fe158b17) ce4233a5-diagnose C->S BackendAPI POST /idle/make-busy [2024-03-22T16:16:42.675794000Z][com.docker.diagnose.exe.ipc][I] (fe158b17) ce4233a5-diagnose C<-S a2ef2f93-BackendAPI POST /idle/make-busy (1.5554ms): 0xc00063e3f0 [2024-03-22T16:16:43.686937000Z][com.docker.diagnose.exe.ipc][I] (e96fb48d) ce4233a5-diagnose C->S BackendAPI GET /idle [2024-03-22T16:16:43.687975600Z][com.docker.diagnose.exe.ipc][I] (e96fb48d) ce4233a5-diagnose C<-S a2ef2f93-BackendAPI GET /idle (1.0386ms): {"apisInFlight":{"/v1.41/containers/04ede05dcb8dcde49f90c569d5a2a378583da7075a72747ac4470b552f8be373/logs":2,"/v1.41/containers/27f045848af73f3e96573234442396e59f6600c3a7526211fc760e00dea878ba/logs":2,"/v1.41/containers/32221562d7bd300ec52e1365e0aadece27b22de229d5f633b9e5fddb5166a3db/json":1,"/v1.41/containers/76377c5d64fc624263e1975f22821a025c313f201372001ec7a716c4b122cff5/logs":2,"/v1.41/containers/84b939fe6c5a4088b7a8290ee92f434becf43b3fa1ce6493ff2acd50b8e3583a/logs":2,"/v1.41/containers/8de087dbbf6ef4731aaf0de7257153c8a58c29b2c38b3e0e65a02bcf5f14408f/logs":2,"/v1.41/containers/c80a3e65fdd2ac82c4acb1e1af2b4db2eb00de7b85eb124a3671d2992c4bf738/logs":2,"/v1.41/containers/d8b3de7f9a937e62cd6c0abd74e3ac85ac3a3a4d7305c5c3454e4054b5eb5c26/logs":2,"/v1.41/containers/ff7402f5e37b99d881408442684c83d8a1300c5e5cc39d03d9911f9e8d86ec49/logs":2,"/v1.44/containers/32221562d7bd/stats":42,"/v1.44/containers/32221562d7bd300ec52e1365e0aadece27b22de229d5f633b9e5fddb5166a3db/start":1,"/v1.44/containers/c80a3e65fdd2ac82c4acb1e1af2b4db2eb00de7b85eb124a3671d2992c4bf738/logs":1},"booted":true,"busyReason":["8 container(s)","in-flight APIs: map[/v1.41/containers/04ede05dcb8dcde49f90c569d5a2a378583da7075a72747ac4470b552f8be373/logs:2 /v1.41/containers/27f045848af73f3e96573234442396e59f6600c3a7526211fc760e00dea878ba/logs:2 /v1.41/containers/32221562d7bd300ec52e1365e0aadece27b22de229d5f633b9e5fddb5166a3db/json:1 /v1.41/containers/76377c5d64fc624263e1975f22821a025c313f201372001ec7a716c4b122cff5/logs:2 /v1.41/containers/84b939fe6c5a4088b7a8290ee92f434becf43b3fa1ce6493ff2acd50b8e3583a/logs:2 /v1.41/containers/8de087dbbf6ef4731aaf0de7257153c8a58c29b2c38b3e0e65a02bcf5f14408f/logs:2 /v1.41/containers/c80a3e65fdd2ac82c4acb1e1af2b4db2eb00de7b85eb124a3671d2992c4bf738/logs:2 /v1.41/containers/d8b3de7f9a937e62cd6c0abd74e3ac85ac3a3a4d7305c5c3454e4054b5eb5c26/logs:2 /v1.41/containers/ff7402f5e37b99d881408442684c83d8a1300c5e5cc39d03d9911f9e8d86ec49/logs:2 /v1.44/containers/32221562d7bd/stats:42 /v1.44/containers/32221562d7bd300ec52e1365e0aadece27b22de229d5f633b9e5fddb5166a3db/start:1 /v1.44/containers/c80a3e65fdd2ac82c4acb1e1af2b4db2eb00de7b85eb124a3671d2992c4bf738/logs:1]","timed activities: map[/idle/make-busy:28.9878227s]"],"containers":8,"idle":"bool","kubernetesEnabled":false,"reduced":false,"services":0,"timedActivities":{"/idle/make-busy":"float64"},"vmPaused":false,"vmRunning":true,"vmStopped":false,"windowsContainers":false} [PASS] DD0027: is there available disk space on the host? [SKIP] DD0028: is there available VM disk space? [PASS] DD0002: does the bootloader have virtualization enabled? [PASS] DD0020: is the Hyper-V Windows Feature enabled? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0013: is the $PATH ok? [PASS] DD0003: is the Docker CLI working? [PASS] DD0005: is the user in the docker-users group? [PASS] DD0038: is the connection to Docker working? [PASS] DD0014: are the backend processes running? [PASS] DD0007: is the backend responding? [SKIP] DD0009: is the vpnkit API responding? [PASS] DD0010: is the Docker API proxy responding? [PASS] DD0006: is the Docker Desktop Service responding? [SKIP] DD0030: is the image access management authorized? [PASS] DD0033: does the host have Internet access? [PASS] DD0002: does the bootloader have virtualization enabled? [PASS] DD0020: is the Hyper-V Windows Feature enabled? [PASS] DD0018: does the host support virtualization? [PASS] DD0001: is the application running? [PASS] DD0017: can a VM be started? [PASS] DD0016: is the LinuxKit VM running? [PASS] DD0011: are the LinuxKit services running? [PASS] DD0004: is the Docker engine running? [PASS] DD0015: are the binary symlinks installed? [PASS] DD0031: does the Docker API work? [PASS] DD0032: do Docker networks overlap with host IPs? No fatal errors detected.
Steps to reproduce the behavior Start the Docker Desktop Start the containers. Run the stack (php, mysql, redis) After several hours, some containers just hang.
Other issues that may be related to this https://github.com/docker/for-win/issues/13894 https://github.com/docker/for-win/issues/13911 https://github.com/docker/for-win/issues/13849
Same :(
- Win 10 pro 10.0.19045
- Hyper-V mode (not wsl)
- Docker Desktop 4.28.0/4.29.0
- Diagnostics ID: 2DF41583-B9D5-4ABA-9BF1-47B13A400E71/20240422054150
com.docker.diagnose.exe" check
Starting diagnostics
[2024-04-22T05:42:54.245415000Z][com.docker.diagnose.exe.ipc][I] 798ee4a3-diagnose -> \\.\pipe\dockerBackendApiServer BackendAPI
[2024-04-22T05:42:54.249400800Z][com.docker.diagnose.exe.ipc][I] (3b75bab7) 798ee4a3-diagnose C->S BackendAPI POST /idle/make-busy
[2024-04-22T05:42:54.250590600Z][com.docker.diagnose.exe.ipc][I] (3b75bab7) 798ee4a3-diagnose C<-S a2b0ca63-BackendAPI POST /idle/make-busy (1.1898ms): 0xc000025a10
[2024-04-22T05:42:55.250406900Z][com.docker.diagnose.exe.ipc][I] (20a9a97a) 798ee4a3-diagnose C->S BackendAPI GET /idle
[2024-04-22T05:42:55.253713000Z][com.docker.diagnose.exe.ipc][I] (20a9a97a) 798ee4a3-diagnose C<-S a2b0ca63-BackendAPI GET /idle (2.9997ms): {"apisInFlight":{"/v1.45/containers/bba059ee09fb5f0422170dca1eeac7e077681f3574e548a7d2b49ec94ebd2ae0/attach":1,"/v1.45/containers/bba059ee09fb5f0422170dca1eeac7e077681f3574e548a7d2b49ec94ebd2ae0/logs":2},"booted":true,"busyReason":["1 container(s)","in-flight APIs: map[/v1.45/containers/bba059ee09fb5f0422170dca1eeac7e077681f3574e548a7d2b49ec94ebd2ae0/attach:1 /v1.45/containers/bba059ee09fb5f0422170dca1eeac7e077681f3574e548a7d2b49ec94ebd2ae0/logs:2]","timed activities: map[/idle/make-busy:28.9982151s]"],"containers":1,"idle":"bool","kubernetesEnabled":false,"reduced":false,"services":0,"timedActivities":{"/idle/make-busy":"float64"},"vmPaused":false,"vmRunning":true,"vmStopped":false,"windowsContainers":false}
[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0020: is the Hyper-V Windows Feature enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[FAIL] DD0004: is the Docker engine running? unable to create docker client: protocol not available
[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] DD0038: is the connection to Docker working? prereq failed: is the Docker engine running?
[PASS] DD0014: are the backend processes running?
[PASS] DD0007: is the backend responding?
[SKIP] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] 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] DD0020: is the Hyper-V Windows Feature enabled?
[PASS] DD0018: does the host support virtualization?
[PASS] DD0001: is the application running?
[PASS] DD0017: can a VM be started?
[PASS] DD0016: is the LinuxKit VM running?
[WARN] DD0004: is the Docker engine running? unable to create docker client: protocol not available
[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: unable to create docker client: protocol not available
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 1 issue:
1 : The test: is the Docker engine running?
Failed with: unable to create docker client: protocol not available
The Docker engine manages all containers and images on the host. Check the dockerd.log to see why it failed to start.
dockerd.log
[2024-04-21T04:48:20.144382300Z][dockerd][I] time="2024-04-21T04:48:20.144313400Z" level=info msg="Starting up"
[2024-04-21T04:48:20.236138000Z][dockerd][I] time="2024-04-21T04:48:20.236085300Z" level=info msg="[graphdriver] using prior storage driver: overlay2"
[2024-04-21T04:48:20.291189200Z][dockerd][I] time="2024-04-21T04:48:20.291111900Z" level=info msg="Loading containers: start."
[2024-04-21T04:48:20.479743600Z][dockerd][I] time="2024-04-21T04:48:20.479662800Z" level=info msg="Default bridge (docker0) is assigned with an IP address 172.17.0.0/16. Daemon option --bip can be used to set a preferred IP address"
[2024-04-21T04:48:20.510321800Z][dockerd][I] time="2024-04-21T04:48:20.510269200Z" level=info msg="Loading containers: done."
[2024-04-21T04:48:20.520281500Z][dockerd][I] time="2024-04-21T04:48:20.520241100Z" level=warning msg="WARNING: daemon is not using the default seccomp profile"
[2024-04-21T04:48:20.520304700Z][dockerd][I] time="2024-04-21T04:48:20.520279800Z" level=info msg="Docker daemon" commit=8b79278 containerd-snapshotter=false storage-driver=overlay2 version=26.0.0
[2024-04-21T04:48:20.520618900Z][dockerd][I] time="2024-04-21T04:48:20.520578100Z" level=info msg="Daemon has completed initialization"
[2024-04-21T04:48:20.656382700Z][dockerd][I] time="2024-04-21T04:48:20.656189300Z" level=info msg="API listen on /run/guest-services/docker.sock"
[2024-04-21T04:48:20.656731400Z][dockerd][I] time="2024-04-21T04:48:20.656685600Z" level=info msg="API listen on /var/run/docker.sock"
[2024-04-21T04:48:20.662087000Z][dockerd][I] time="2024-04-21T04:48:20.662042900Z" level=error msg="Handler for GET /v1.45/services returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again." spanID=752af67b13ade83c traceID=ecb78e2ea4963767a4452e13f62191c7
[2024-04-21T04:48:20.683529600Z][dockerd][I] time="2024-04-21T04:48:20.683478900Z" level=error msg="Handler for GET /v1.45/services returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again." spanID=87b66dcddc961268 traceID=12f30ff6e374f6a65b44cf8f33a0e824
[2024-04-21T04:48:20.685063000Z][dockerd][I] time="2024-04-21T04:48:20.684984900Z" level=error msg="Handler for GET /v1.45/services returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again." spanID=4752ab086fed8698 traceID=4b1df876075f90f140eaf1bd87b5bfa3
[2024-04-21T04:50:00.863161000Z][dockerd][I] 2024/04/21 04:50:00 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:00.863162600Z][dockerd][I] 2024/04/21 04:50:00 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:00.863168700Z][dockerd][I] 2024/04/21 04:50:00 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:00.863189200Z][dockerd][I] 2024/04/21 04:50:00 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:00.863192100Z][dockerd][I] 2024/04/21 04:50:00 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:00.863194100Z][dockerd][I] 2024/04/21 04:50:00 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:00.863194300Z][dockerd][I] 2024/04/21 04:50:00 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:00.863235400Z][dockerd][I] 2024/04/21 04:50:00 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:01.061273200Z][dockerd][I] 2024/04/21 04:50:01 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:01.061290100Z][dockerd][I] 2024/04/21 04:50:01 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:01.061295600Z][dockerd][I] 2024/04/21 04:50:01 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:01.061296000Z][dockerd][I] 2024/04/21 04:50:01 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T04:50:01.090951500Z][dockerd][I] time="2024-04-21T04:50:01.090912300Z" level=info msg="ignoring event" container=b3f76b5530b827e61428173cd125dddb4e359709b7159951693f5cba12315984 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
[2024-04-21T05:00:46.819643900Z][dockerd][I] time="2024-04-21T05:00:46.819602200Z" level=warning msg="failed to delete process" container=d4da3f7963f1a39c8872127ab19a416aab6c54ff4beaa8886dccd9ee98024a6a error="ttrpc: closed: unknown" process=eb7b7a9d9300781ab843d634fd44b8c295a10f43cb47059f7be28d561f929841
[2024-04-21T05:00:46.819645500Z][dockerd][I] time="2024-04-21T05:00:46.819619200Z" level=info msg="ignoring event" container=d4da3f7963f1a39c8872127ab19a416aab6c54ff4beaa8886dccd9ee98024a6a module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
[2024-04-21T05:00:49.896363400Z][dockerd][I] 2024/04/21 05:00:49 http: superfluous response.WriteHeader call from go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp.(*respWriterWrapper).WriteHeader (wrap.go:98)
[2024-04-21T05:00:49.909917400Z][dockerd][I] time="2024-04-21T05:00:49.909871700Z" level=info msg="ignoring event" container=ae0870a0dce5c921db2e6201d148217cd94d764011876ec374512d4203ebaf30 module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
[2024-04-22T05:41:06.821693400Z][dockerd][I] time="2024-04-22T05:41:06.821625800Z" level=error msg="stream copy error: reading from a closed fifo"
[2024-04-22T05:41:06.823542600Z][dockerd][I] time="2024-04-22T05:41:06.823491500Z" level=error msg="Error running exec 92f1eb448dc9cff16869236f432f0f9b88dec596ef5b347ce51e51ca68b6fcd9 in container: OCI runtime exec failed: exec failed: unable to start container process: error executing setns process: exit status 1: unknown" spanID=00b99d10b44a30a5 traceID=de2ec41e81bba004b0fa5237b0720f9d
[2024-04-22T05:41:06.824039800Z][dockerd][I] time="2024-04-22T05:41:06.823971900Z" level=error msg="failed to close container stdin" container=bba059ee09fb5f0422170dca1eeac7e077681f3574e548a7d2b49ec94ebd2ae0 error="process does not exist 92f1eb448dc9cff16869236f432f0f9b88dec596ef5b347ce51e51ca68b6fcd9: not found" module=libcontainerd namespace=moby
[2024-04-22T05:41:16.797486500Z][dockerd][I] time="2024-04-22T05:41:16.797380500Z" level=info msg="Container failed to exit within 10s of signal 15 - using the force" container=bba059ee09fb5f0422170dca1eeac7e077681f3574e548a7d2b49ec94ebd2ae0 spanID=f265bb2559d27768 traceID=b33dbf8063e6e609e8f4a48cd1838633
[2024-04-22T05:41:26.806514400Z][dockerd][I] time="2024-04-22T05:41:26.806410300Z" level=warning msg="Container failed to exit within 10s of kill - trying direct SIGKILL" container=bba059ee09fb5f0422170dca1eeac7e077681f3574e548a7d2b49ec94ebd2ae0 error="context deadline exceeded"
[2024-04-22T05:41:30.808605000Z][dockerd][I] time="2024-04-22T05:41:30.808455900Z" level=error msg="error killing container: context deadline exceeded" container=bba059ee09fb5f0422170dca1eeac7e077681f3574e548a7d2b49ec94ebd2ae0 error="tried to kill container, but did not receive an exit event" spanID=f265bb2559d27768 traceID=b33dbf8063e6e609e8f4a48cd1838633
[2024-04-22T05:41:30.808697300Z][dockerd][I] time="2024-04-22T05:41:30.808564800Z" level=error msg="Handler for POST /v1.45/containers/bba059ee09fb5f0422170dca1eeac7e077681f3574e548a7d2b49ec94ebd2ae0/stop returned error: cannot stop container: bba059ee09fb5f0422170dca1eeac7e077681f3574e548a7d2b49ec94ebd2ae0: tried to kill container, but did not receive an exit event" spanID=f265bb2559d27768 traceID=b33dbf8063e6e609e8f4a48cd1838633
[2024-04-22T05:42:00.355747200Z][dockerd][I] time="2024-04-22T05:42:00.355698000Z" level=error msg="Handler for GET /v1.43/nodes returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again." spanID=f51c62e01e5bca7b traceID=e0cfa7590586d2d825652deffdebb786
[2024-04-22T05:42:00.359485700Z][dockerd][I] time="2024-04-22T05:42:00.359442600Z" level=error msg="Handler for GET /v1.43/services returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again." spanID=25ade9156562d56b traceID=d5687040b11193b080111e2be2216dc8
[2024-04-22T05:42:04.818529300Z][dockerd][I] time="2024-04-22T05:42:04.818480800Z" level=error msg="Handler for GET /v1.43/nodes returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again." spanID=2dcfbb98d3826d97 traceID=b2c41275597c25a61be96f91cd5a46eb
[2024-04-22T05:42:04.818909000Z][dockerd][I] time="2024-04-22T05:42:04.818872900Z" level=error msg="Handler for GET /v1.43/services returned error: This node is not a swarm manager. Use \"docker swarm init\" or \"docker swarm join\" to connect this node to swarm and try again." spanID=53fc65093523b340 traceID=0b344fa9b9cbabb832e063ef10ebabba
Also having this issue, stull trying to figure out what is goging on. The Docker desktop interface responds, only the containers stop responding.
- 16 GB ram (87% used)
- Windows 10 Enterprise 22H2
- Docker Desktop 4.2.9 (hyper-v)
Also having this issue, even with 4.30.0 among other strange bugs mentioned in other tickets.
Currently on 4.29. Got a RAM upgrade from 16gb to 32gb. The issue persists. Sometimes I need to restart Docker at least twice to make it work properly.
I reverted to 4.24.0 and it works fine. I'm not going to update in near future :)
@fikusz01 @marianomd Might be worth opening a separate issue for that one if you have the time - it looks like there is a new HyperV-related issue introduced relatively recently (a couple on our team have had that recently), but the main issue being discussed in this ticket is WSL-specific, and has been around for a few years now (ie: well before 4.24.0 - the original message noted it in 4.15.0)
Had to downgrade from 4.29 to version 4.24.2. Working fine for the last few days. Running on Windows 11, on HyperV.
To downgrade without unistalling, I had to:
- Download the desired version
- Open Command Prompt on Windows and ran (source):
'.\Docker Desktop Installer.exe' install --disable-version-check - The installation prompted to terminate the currently active Docker process.
- The installation completed as anticipated, without any data loss.
I didn't try other versions. Check this list, curated by another user.
I gave it a shot and installed 4.33.1. Working properly so far. No hang ups yet.