-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
containerd-shim-runc-v2 exit abnormally #6402
Labels
Comments
This was referenced Jan 16, 2022
closed by #6452 |
fuweid
added a commit
to fuweid/containerd
that referenced
this issue
Feb 20, 2022
If containerd-shim-runc-v1 process dead abnormally, such as received kill -s 9 signal, panic or other unkown reasons, the containerd-shim-runc-v1 server can not reap runc container and forward init process exit event. This will lead the container leaked in dockerd. When shim dead, containerd will clean dead shim, here read init process pid and forward exit event with pid at the same time. Related to: containerd#6402 Signed-off-by: Jeff Zvier <zvier20@gmail.com> Signed-off-by: Wei Fu <fuweid89@gmail.com>
fuweid
added a commit
to fuweid/containerd
that referenced
this issue
Feb 20, 2022
If containerd-shim-runc-v1 process dead abnormally, such as received kill -s 9 signal, panic or other unkown reasons, the containerd-shim-runc-v1 server can not reap runc container and forward init process exit event. This will lead the container leaked in dockerd. When shim dead, containerd will clean dead shim, here read init process pid and forward exit event with pid at the same time. Related to: containerd#6402 Signed-off-by: Jeff Zvier <zvier20@gmail.com> Signed-off-by: Wei Fu <fuweid89@gmail.com> (cherry picked from commit 7901f4b) Signed-off-by: Wei Fu <fuweid89@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We cause an strange phenomenon that the container's containerd-shim-runc-v2 and process inside the container both exit, but docker ps can still list this container with Up state.
The containerd's log about it is:
And we can sure that the dockerd not stop or kill the container initiatively. It seems like that the shim exit first, but no more information about how it works abnormal.
Steps to reproduce the issue
Not find the accurate way to reproduce this issue. Kill containerd-shim-runc-v2 can product the same phenomenon .
If use containerd-shim, there is no this problem.
Describe the results you received and expected
First, if the containerd-shim-runc-v2 process exit about the container, I think the containerd need to publish TaskExit and TaskDelete event to dockerd to clean this dead container.
What problems may cause containerd-shim-runc-v2 exit anomaly ? May be this is a system problem, because all the containers on the host had this issue at the same time.
What version of containerd are you using?
1.4.3
Any other relevant information
runc --version
uname -r
Show configuration if it is related to CRI plugin.
The text was updated successfully, but these errors were encountered: