mirror of
https://github.com/containers/podman.git
synced 2025-08-06 03:19:52 +08:00

For systems that have extreme robustness requirements (edge devices, particularly those in difficult to access environments), it is important that applications continue running in all circumstances. When the application fails, Podman must restart it automatically to provide this robustness. Otherwise, these devices may require customer IT to physically gain access to restart, which can be prohibitively difficult. Add a new `--on-failure` flag that supports four actions: - **none**: Take no action. - **kill**: Kill the container. - **restart**: Restart the container. Do not combine the `restart` action with the `--restart` flag. When running inside of a systemd unit, consider using the `kill` or `stop` action instead to make use of systemd's restart policy. - **stop**: Stop the container. To remain backwards compatible, **none** is the default action. Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
461 B
461 B
--health-on-failure=action
Action to take once the container transitions to an unhealthy state. The default is none.
- none: Take no action.
- kill: Kill the container.
- restart: Restart the container. Do not combine the
restart
action with the--restart
flag. When running inside of a systemd unit, consider using thekill
orstop
action instead to make use of systemd's restart policy. - stop: Stop the container.