mirror of
https://github.com/containers/podman.git
synced 2025-12-02 02:58:03 +08:00
a1249425bd
New flags in a `podman update` can change the configuration of HealthCheck when the container is started, without having to restart or recreate the container. This can help determine why a given container suddenly started failing HealthCheck without interfering with the services it provides. For example, reconfigure HealthCheck to keep logs longer than the usual last X results, store logs to other destinations, etc. Fixes: https://issues.redhat.com/browse/RHEL-60561 Signed-off-by: Jan Rodák <hony.com@seznam.cz>
616 B
616 B
####> This option file is used in: ####> podman create, run, update ####> If file is edited, make sure the changes ####> are applicable to all of those.
--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
restartaction with the--restartflag. When running inside of a systemd unit, consider using thekillorstopaction instead to make use of systemd's restart policy. - stop: Stop the container.