mirror of
https://github.com/containers/podman.git
synced 2025-06-03 20:33:20 +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>
12 lines
852 B
Markdown
12 lines
852 B
Markdown
####> 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-startup-cmd**=*"command"* | *'["command", "arg1", ...]'*
|
|
|
|
Set a startup healthcheck command for a container. This command is executed inside the container and is used to gate the regular
|
|
healthcheck. When the startup command succeeds, the regular healthcheck begins and the startup healthcheck ceases. Optionally,
|
|
if the command fails for a set number of attempts, the container is restarted. A startup healthcheck can be used to ensure that
|
|
containers with an extended startup period are not marked as unhealthy until they are fully started. Startup healthchecks can only be
|
|
used when a regular healthcheck (from the container's image or the **--health-cmd** option) is also set.
|