You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you run podman kube down or podman play kube --down the constituent containers are immediately terminated with a SIGKILL regardless of the container's StopTimeout and StopSignal
Steps to reproduce the issue
Steps to reproduce the issue
Create a pod with podman kube play. Use an image whose behavior differs based on how it terminates
Observe that the created container has the default StopTimeout=10 and default StopSignal=15 (sigterm)
Watch pod logs with podman logs -f
Tear down pod with podman kube down
Describe the results you received
The container is immediately stopped with a SIGKILL, not SIGTERM
Describe the results you expected
The container should receive StopSignal, followed by a SIGKILL after StopTimeout if container hasn't exited.
Issue Description
If you run
podman kube down
orpodman play kube --down
the constituent containers are immediately terminated with a SIGKILL regardless of the container's StopTimeout and StopSignalSteps to reproduce the issue
Steps to reproduce the issue
podman kube play
. Use an image whose behavior differs based on how it terminatespodman logs -f
podman kube down
Describe the results you received
The container is immediately stopped with a SIGKILL, not SIGTERM
Describe the results you expected
The container should receive StopSignal, followed by a SIGKILL after StopTimeout if container hasn't exited.
podman info output
Podman in a container
No
Privileged Or Rootless
Privileged
Upstream Latest Release
No
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: