Open Bevisy opened 2 weeks ago
The fact that it works with runc and conmon-rs makes me wonder what crun does differently.
OTOH the above use case works pretty well when using:
what is the command line used by conmon-rs to run crun?
I added some debug statement to conmon-rs and it runs:
crun \
--root=/run/runc \
--systemd-cgroup \
create \
--bundle /run/containers/storage/overlay-containers/dc31d87ed3b6530f23411374f44d4d84b4da8812d8af9b0e90258e04eb2ad03f/userdata \
--pid-file /run/containers/storage/overlay-containers/dc31d87ed3b6530f23411374f44d4d84b4da8812d8af9b0e90258e04eb2ad03f/userdata/pidfile \
dc31d87ed3b6530f23411374f44d4d84b4da8812d8af9b0e90258e04eb2ad03f
thanks. The command line looks correct
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.
However, this issue does not occur when using runc:
So, what could be the reason for this?
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.)