-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
runc-shim-v2 hold lock cause cri can't delete container #10092
Labels
Comments
ningmingxiao
changed the title
shim-v2 hold lock cause cri can't delete container
runc-shim-v2 hold lock cause cri can't delete container
Apr 19, 2024
@ningmingxiao you can use https://github.com/linuxerwang/goroutine-inspect to de-duplicate the goroutines and find which goroutine hold the lock. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
pod have a pause container (53fd29e212f3) and nginx container (509e39bd68c0)
53fd29 containerd log
509e39bd68c0 containerd log
shim-v2 stack
shim_stack.log
Steps to reproduce the issue
It is defficlut to reproduce
Describe the results you received and expected
shim can release lock
What version of containerd are you using?
1.7.6
Any other relevant information
No response
Show configuration if it is related to CRI plugin.
No response
The text was updated successfully, but these errors were encountered: