Docker compatible /containers/<id or name>/stop
does not support negative timeouts
#17542
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Issue Description
The Docker compatible
/containers/<id or name>/stop
endpoint does not support using a negative timeout. Docker's spec for this endpoint states that you can "use '-1' to wait indefinitely." rather then having a set timeout after which the container will be killed. Podman's implementation of this endpoint utilizes auint
rather then anint
, causing a error to be thrown when using negative values.Steps to reproduce the issue
Steps to reproduce the issue
-1
(if using the Docker Go SDK this will need to be-1 * time.Second
)Describe the results you received
Request returns an error and the container continues to run.
Describe the results you expected
Container is sent a stop signal and is not terminated immediately or after a default timeout.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: