Hi, I have a container where I have my own program as init replacement. It takes the responsibility of shutting down all my services properly (one of them being MySQL). Sometimes some services need more than the default 10 seconds that podman stop command has before it resorts to SIGKILL. So while playing with various timeout, I get a strange result with I use -1 (supposed to be for infinite wait). Giving -1 results in immediate SIGKILL $ podman stop -t -1 indimail-mta WARN[0000] StopSignal SIGTERM failed to stop container indimail-mta in 18446744073709551615 seconds, resorting to SIGKILL indimail-mta Looks like unsigned 64 bit integer has been used for something which can have negative value -- Regards Manvendra - http://www.indimail.org GPG Pub Key http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xC7CBC760014D250C _______________________________________________ Podman mailing list -- podman(a)lists.podman.io To unsubscribe send an email to podman-leave(a)lists.podman.io

On Sun, 25 Feb 2024 at 20:09, Brent Baude <bbaude(a)redhat.com&gt; wrote: > > Your best bet would be to file an issue at https://github.com/containers/podman. OK. Will do that > The documentation does not mention anything about a -1 having a specific mean. And the uint is used right away as the StopOption type for Timeout. The online documentation https://docs.podman.io/en/stable/markdown/podman-stop.1.html does mention this --time, -t=seconds Seconds to wait before forcibly stopping the container. Use -1 for infinite wait.