mirror of
https://github.com/containers/podman.git
synced 2025-11-03 15:56:51 +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>
20 lines
1.1 KiB
Markdown
20 lines
1.1 KiB
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.
|
|
#### **--restart**=*policy*
|
|
|
|
Restart policy to follow when containers exit.
|
|
Restart policy will not take effect if a container is stopped via the **podman kill** or **podman stop** commands.
|
|
|
|
Valid _policy_ values are:
|
|
|
|
- `no` : Do not restart containers on exit
|
|
- `on-failure[:max_retries]` : Restart containers when they exit with a non-zero exit code, retrying indefinitely or until the optional *max_retries* count is hit
|
|
- `always` : Restart containers when they exit, regardless of status, retrying indefinitely
|
|
- `unless-stopped` : Identical to **always**
|
|
|
|
Please note that restart will not restart containers after a system reboot.
|
|
If this functionality is required in your environment, you can invoke Podman from a **systemd.unit**(5) file, or create an init script for whichever init system is in use.
|
|
To generate systemd unit files, please see **podman generate systemd**.
|