You are not logged in.
Pages: 1
Hi,
I have a headless arch vm under proxmox for my homelab. I noticed that if i try to reboot it, either with "sudo reboot" or with the reboot option in proxmox, it hangs forever ( or for more that i have the patience to wait) with the message that a process with a certain pid is not stopping (sd-close). After a bit of investigation i found out that the hung process is related either to docker.service or docker.socket, since if stop them it reboot just fine. I would like to be able to reboot the machine without manually stopping those services first, even if there are several containers running, because it is useful to do so from the proxmox's interface from time to time.
Here's docker.service:
└─> systemctl status docker.service
● docker.service - Docker Application Container Engine
Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; preset: disabled)
Active: active (running) since Sat 2024-06-08 09:59:56 CEST; 13min ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 606 (dockerd)
Tasks: 314
Memory: 272.6M (peak: 276.9M)
CPU: 3.598s
CGroup: /system.slice/docker.service
├─ 606 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
├─ 959 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 9443 -container-ip 172.17.0.3 -container-port 9443
├─ 967 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 9443 -container-ip 172.17.0.3 -container-port 9443
├─ 985 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 8000 -container-ip 172.17.0.3 -container-port 8000
├─ 997 /usr/bin/docker-proxy -proto tcp -host-ip :: -host-port 8000 -container-ip 172.17.0.3 -container-port 8000
├─1077 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 2222 -container-ip 172.18.0.5 -container-port 22
and here's docker.socket:
└─> systemctl status docker.socket
● docker.socket - Docker Socket for the API
Loaded: loaded (/usr/lib/systemd/system/docker.socket; disabled; preset: disabled)
Active: active (running) since Sat 2024-06-08 09:59:52 CEST; 16min ago
Triggers: ● docker.service
Listen: /run/docker.sock (Stream)
Tasks: 0 (limit: 38495)
Memory: 0B (peak: 256.0K)
CPU: 1ms
CGroup: /system.slice/docker.socket
Jun 08 09:59:52 mobydick systemd[1]: Starting Docker Socket for the API...
Jun 08 09:59:52 mobydick systemd[1]: Listening on Docker Socket for the API.
Offline
Did you enable live-restore?
* Good formatted problem description will cause good and quick solution
* Please don't forget to mark as [SOLVED].
Offline
Pages: 1