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
zombie containerd-shim processes #318
Comments
The simplest "fix" (workaround) for this repository is something like adjusting |
(If you don't trust our entrypoint script [which, fair], you can also reproduce just the same with |
Temporary workaround is up in #319 (to just throw |
Did you open a ticket in containerd as well? (of the existing ones don't match this scenario?) |
I didn't file an issue there yet, but I've commented at containerd/containerd#5708 (comment) now (because it feels way too similar to be coincidence, IMO). |
Quoting containerd/containerd#5708 (comment) here for posterity:
|
FWIW, I can still reproduce (using $ docker run -dit --privileged --name test --entrypoint dockerd --pull=always docker:dind
dind: Pulling from library/docker
Digest: sha256:a7a9383d0631b5f6b59f0a8138912d20b63c9320127e3fb065cb9ca0257a58b2
Status: Downloaded newer image for docker:dind
41749ef585c457ff1e737f7ef2efc6ac8d3395219a6526c25f042c31bc43ca01
$ docker exec test ps faux
PID USER TIME COMMAND
1 root 0:00 dockerd
22 root 0:00 containerd --config /var/run/docker/containerd/containerd.toml --log-level info
138 root 0:00 ps faux
$ docker exec test docker run --rm tianon/true
Unable to find image 'tianon/true:latest' locally
latest: Pulling from tianon/true
c53fb220cbad: Pulling fs layer
c53fb220cbad: Download complete
c53fb220cbad: Pull complete
Digest: sha256:009cce421096698832595ce039aa13fa44327d96beedb84282a69d3dbcf5a81b
Status: Downloaded newer image for tianon/true:latest
$ docker exec test ps faux
PID USER TIME COMMAND
1 root 0:00 dockerd
22 root 0:00 containerd --config /var/run/docker/containerd/containerd.toml --log-level info
196 root 0:00 [containerd-shim]
270 root 0:00 ps faux
$ docker exec test docker run --rm tianon/true
$ docker exec test ps faux
PID USER TIME COMMAND
1 root 0:00 dockerd
22 root 0:00 containerd --config /var/run/docker/containerd/containerd.toml --log-level info
196 root 0:00 [containerd-shim]
303 root 0:00 [containerd-shim]
376 root 0:00 ps faux
$ docker exec test docker version
Client:
Version: 20.10.17
API version: 1.41
Go version: go1.17.11
Git commit: 100c701
Built: Mon Jun 6 22:56:42 2022
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.17
API version: 1.41 (minimum version 1.12)
Go version: go1.17.11
Git commit: a89b842
Built: Mon Jun 6 23:01:45 2022
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v1.6.6
GitCommit: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
runc:
Version: 1.1.2
GitCommit: v1.1.2-0-ga916309f
docker-init:
Version: 0.19.0
GitCommit: de40ad0 |
dockerd might fail from time to time which looks related to the known issue docker-library/docker#318 and using docker-init is the workaround used by the community Changelog: None Ticket: QA-508 Signed-off-by: Alex Miliukov <oleksandr.miliukov@northern.tech>
dockerd might fail from time to time which looks related to the known issue docker-library/docker#318 and using docker-init is the workaround used by the community Changelog: None Ticket: QA-508 Signed-off-by: Alex Miliukov <oleksandr.miliukov@northern.tech>
If I do the same test with
--init
or... docker:20-dind docker-init dockerd
, then we get no zombies.I think this is technically a bug in containerd, because I can reproduce with bare
containerd
as pid1 as well, but it doesn't seem quite the same as containerd/containerd#5708 (although perhaps related).cc @thaJeztah @cpuguy83
The text was updated successfully, but these errors were encountered: