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
When a program is running as PID 1, its default SIGTERM and SIGINT handlers ignore the signal completely, instead of exiting.
As the program is running as PID 1 in the container, and does not set its own handlers for these signals, it ignores them, which makes it unnecessarily take longer to stop the container, as podman/docker waits some time after sending SIGTERM before resorting to SIGKILL.
The program should set its own handlers for SIGTERM and SIGINT, which do the necessary cleanup (if necessary) and exit.
The text was updated successfully, but these errors were encountered:
When a program is running as PID 1, its default SIGTERM and SIGINT handlers ignore the signal completely, instead of exiting.
As the program is running as PID 1 in the container, and does not set its own handlers for these signals, it ignores them, which makes it unnecessarily take longer to stop the container, as podman/docker waits some time after sending SIGTERM before resorting to SIGKILL.
The program should set its own handlers for SIGTERM and SIGINT, which do the necessary cleanup (if necessary) and exit.
The text was updated successfully, but these errors were encountered: