liveBook · Manning

Stop signal

As explained in Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more

A stop signal is the signal configuration that a container engine sends to request orderly termination of the container's main process.

A stop signal is the signal configuration Podman sends to a container’s primary process, PID 1, to request orderly termination. section 2.1.3

Podman’s default stopping sequence is:

  • Send SIGTERM, usually, to PID 1. section 2.1.3
  • Wait 10 seconds for cleanup and committed changes. section 2.1.3
  • Send SIGKILL if the process remains running; use -t 0 to skip the wait. section 2.1.3

Systemd containers

Systemd ignores SIGTERM and shuts down with SIGRTMIN+3, signal 37. Podman configures this stop signal for systemd-mode containers; inspect it with podman inspect. section 7.1.2

$ podman stop myapp

Run podman stop myapp for orderly termination, or podman stop -t 0 myapp1 for immediate SIGKILL. section 2.1.3

How Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more covers it

How deep it goes
Explains PID 1 signaling, the default timeout, forced termination, overrides, and systemd-specific behavior.
Examples
Uses podman stop, podman stop -t 0, image inspection, and systemd containers configured with signal 37.
What you can do after
Operate container shutdown with graceful waits, immediate termination, custom signals, and signal inspection.
How it connects
Connects container shutdown with PID 1, SIGTERM, SIGKILL, systemd, and OCI image metadata.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Podman in Action: Secure, rootless containers for Kubernetes, microservices, and more. The section links point to the parts of the book it draws on.