mirror of
https://github.com/containers/podman.git
synced 2025-08-14 02:41:34 +08:00
482ef7bfcf
This is something Docker does, and we did not do until now. Most difficult/annoying part was the REST API, where I did not really want to modify the struct being sent, so I made the new restart policy parameters query parameters instead. Testing was also a bit annoying, because testing restart policy always is. Signed-off-by: Matt Heon <mheon@redhat.com>
23 lines
1.2 KiB
Markdown
23 lines
1.2 KiB
Markdown
####> This option file is used in:
|
|
####> podman create, pod clone, pod create, run, update
|
|
####> If file is edited, make sure the changes
|
|
####> are applicable to all of those.
|
|
#### **--restart**=*policy*
|
|
|
|
Restart policy to follow when containers exit.
|
|
Restart policy does 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
|
|
- `never` : Synonym for **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**
|
|
|
|
Podman provides a systemd unit file, podman-restart.service, which restarts containers after a system reboot.
|
|
|
|
When running containers in systemd services, use the restart functionality provided by systemd.
|
|
In other words, do not use this option in a container unit, instead set the `Restart=` systemd directive in the `[Service]` section.
|
|
See **podman-systemd.unit**(5) and **systemd.service**(5).
|