Open Bevisy opened 3 months ago
I found that it might be due to conmonrs not correctly waiting for the process to exit. https://github.com/containers/conmon-rs/blob/02e270ff2a227562feadb9731dc4e9f840d7638c/conmon-rs/server/src/child_reaper.rs#L120
Indeed this looks like an issue in conmon-rs :thinking:
A friendly reminder that this issue had no activity for 30 days.
A friendly reminder that this issue had no activity for 30 days.
What happened?
using pod-config.json and container-config.json to create pod:
Then, we could find the container was created failed:
At this point, the container process on the node becomes a zombie process, and the pod cannot be deleted.
What did you expect to happen?
Expect the container process to exit normally instead of becoming a zombie process.
How can we reproduce it (as minimally and precisely as possible)?
See what happened.
Anything else we need to know?
No response
CRI-O and Kubernetes version
OS version
Additional environment details (AWS, VirtualBox, physical, etc.)