Describe the bug
When Docker/Podman has to stop the container, nothing happens for 10 seconds until there is a SIGKILL. It is more noticeable when the new recreated container tries to kill the old one to replace it. It is not a big issue, it is just annoying having to wait 10 seconds each time - I cannot seem to change that time span.
podman stop -t 10 api_pylon-app_1
WARN[0010] StopSignal SIGTERM failed to stop container api_pylon-app_1 in 10 seconds, resorting to SIGKILL
api_pylon-app_1
I cannot see anywhere in the docs to handle a SIGTERM. My Nuxt container in comparison exits on SIGTERM.
To Reproduce
Recreate an existing container or stop the running container.
Example:
podman-compose up --build --force-recreate -d pylon-app
podman stop pylon-app
Expected behavior
Graceful shutdown.
Additional context
Bun version 1.2.20.
Pylon version ^2.0.0.
Pylon Dev version 1.0.6.
Describe the bug
When Docker/Podman has to stop the container, nothing happens for 10 seconds until there is a SIGKILL. It is more noticeable when the new recreated container tries to kill the old one to replace it. It is not a big issue, it is just annoying having to wait 10 seconds each time - I cannot seem to change that time span.
podman stop -t 10 api_pylon-app_1 WARN[0010] StopSignal SIGTERM failed to stop container api_pylon-app_1 in 10 seconds, resorting to SIGKILL api_pylon-app_1I cannot see anywhere in the docs to handle a SIGTERM. My Nuxt container in comparison exits on SIGTERM.
To Reproduce
Recreate an existing container or stop the running container.
Example:
Expected behavior
Graceful shutdown.
Additional context
Bun version
1.2.20.Pylon version
^2.0.0.Pylon Dev version
1.0.6.