Files
podman/docs/source/markdown/options/health-timeout.md
Jan Rodák b5a1b512c9 Fix overwriting the Healthcheck configuration from the image
If the --health-cmd flag is not specified, other flags such as --health-interval, --health-timeout, --health-retries, and --health-start-period are ignored if the image contains a Healthcheck. This makes it impossible to modify these Healthcheck configuration when a container is created.

Fixes: https://github.com/containers/podman/issues/20212
Fixes: https://issues.redhat.com/browse/RUN-2629

Signed-off-by: Jan Rodák <hony.com@seznam.cz>
2025-04-03 15:52:05 +02:00

721 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-timeout=timeout

The maximum time allowed to complete the healthcheck before an interval is considered failed. Like start-period, the value can be expressed in a time format such as 1m22s. The default value is 30s.

Note: A timeout marks the healthcheck as failed but does not terminate the running process. This ensures that a slow but eventually successful healthcheck does not disrupt the container but is still accounted for in the health status.

Note: This parameter will overwrite related healthcheck configuration from the image.