mirror of
https://github.com/containers/podman.git
synced 2025-10-28 03:45:54 +08:00
c9c2f644da
In each options/foo.md, keep a list of where the option is used. This will be valuable to anyone making future edits, and to those reviewing those edits. This may be a controversial commit, because those crossref lists are autogenerated as a side effect of the script that reads them. It definitely violates POLA. And one day, some kind person will reconcile (e.g.) --label, using it in more man pages, and maybe forget to git-commit the rewritten file, and CI will fail. I think this is a tough tradeoff, but worth doing. Without this, it's much too easy for someone to change an option file in a way that renders it inapplicable/misleading for some podman commands. Signed-off-by: Ed Santiago <santiago@redhat.com>
13 lines
630 B
Markdown
13 lines
630 B
Markdown
####> This option file is used in:
|
|
####> podman create, run
|
|
####> If you edit this file, make sure your changes
|
|
####> are applicable to all of those.
|
|
#### **--health-cmd**=*"command"* | *'["command", "arg1", ...]'*
|
|
|
|
Set or alter a healthcheck command for a container. The command is a command to be executed inside your
|
|
container that determines your container health. The command is required for other healthcheck options
|
|
to be applied. A value of **none** disables existing healthchecks.
|
|
|
|
Multiple options can be passed in the form of a JSON array; otherwise, the command will be interpreted
|
|
as an argument to **/bin/sh -c**.
|