opensource/podman
1
0
Fork 0
mirror of https://github.com/containers/podman.git synced 2025-08-06 11:32:07 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
podman/docs/source/markdown/options/health-log-destination.md
Jan Rodák a1249425bd Configure HealthCheck with podman update 
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>
2024-11-19 19:44:14 +01:00

769 B
Raw Blame History

####> 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-log-destination=directory_path

Set the destination of the HealthCheck log. Directory path, local or events_logger (local use container state file) (Default: local)

  • local: (default) HealthCheck logs are stored in overlay containers. (For example: $runroot/healthcheck.log)
  • directory: creates a log file named <container-ID>-healthcheck.log with HealthCheck logs in the specified directory.
  • events_logger: The log will be written with logging mechanism set by events_logger. It also saves the log to a default directory, for performance on a system with a large number of logs.