tmp/tmp.X5mtKvYY4Q/src//containerd/containerd/vendor//urfave/cli/app.go:268 +0圆55 tmp/tmp.X5mtKvYY4Q/src//containerd/containerd/vendor//urfave/cli/app.go:502 +0xd4 tmp/tmp.X5mtKvYY4Q/src//containerd/containerd/cmd/containerd/main.go:134 +0x878 tmp/tmp.X5mtKvYY4Q/src//containerd/containerd/cmd/containerd/main_unix.go:30 +0x8b tmp/tmp.X5mtKvYY4Q/src//containerd/containerd/cmd/containerd/main_unix.go:44 +0x2cb tmp/tmp.X5mtKvYY4Q/src//containerd/containerd/cmd/containerd/main_unix.go:69 +0x8c ID: KIY5:X5P2:5FI5:GEPC:Q2OO:XF4P:KFB2:S22T:A76T:DVFV:UIFB:ZATYĭEBU received signal module=containerd signal=user defined signal 1 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslogĬontainerd version: 89623f28b87a6004d4b785663257362d1658a729 Network: bridge host macvlan null overlay
Have docker running, start a container, and check output of ps auxf: docker-containerd and docker-containerd-shim are child-processes of dockerd:
This problem could explain some reports about "unkillable" containers, where everything appears to be running, but interaction is not possible (possibly after containerd was OOM killed, but could have different causes). Error response from daemon: Cannot kill container: testing: Cannot kill container 9bfdba3fc8eee79d6ca5773f7caff5dc5a8379037e98b6ded5c8b68df5750359: connection error: desc = "transport: dial unix /var/run/docker/containerd/docker-containerd.sock: connect: connection refused ": unknownĮrror response from daemon: Could not kill running container 9bfdba3fc8eee79d6ca5773f7caff5dc5a8379037e98b6ded5c8b68df5750359, cannot remove - Cannot kill container 9bfdba3fc8eee79d6ca5773f7caff5dc5a8379037e98b6ded5c8b68df5750359: connection error: desc = "transport: dial unix /var/run/docker/containerd/docker-containerd.sock: connect: connection refused ": unknownīut killing dockerd (either by killall -9 dockerd or a SIGHUP killall -HUP dockerd) restores functionality.
0 kommentar(er)
