mirror of
https://github.com/containers/podman.git
synced 2025-12-01 18:49:18 +08:00
b5a1b512c9
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>
17 lines
998 B
Markdown
17 lines
998 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-start-period**=*period*
|
|
|
|
The initialization time needed for a container to bootstrap. The value can be expressed in time format like
|
|
**2m3s**. The default value is **0s**.
|
|
|
|
Note: The health check command is executed as soon as a container is started, if the health check is successful
|
|
the container's health state will be updated to `healthy`. However, if the health check fails, the health state will
|
|
stay as `starting` until either the health check is successful or until the `--health-start-period` time is over. If the
|
|
health check command fails after the `--health-start-period` time is over, the health state will be updated to `unhealthy`.
|
|
The health check command is executed periodically based on the value of `--health-interval`.
|
|
|
|
Note: This parameter will overwrite related healthcheck configuration from the image.
|