diff options
| author | Valentin Rothberg <rothberg@redhat.com> | 2020-01-09 12:27:24 +0100 |
|---|---|---|
| committer | Valentin Rothberg <rothberg@redhat.com> | 2020-01-09 16:12:12 +0100 |
| commit | 816e50ba02837946afade83e3cad06dd44d213ec (patch) | |
| tree | 67834eb73ab890cb4c9fba8d37f68e3fdec9dcd6 /docs/source/markdown | |
| parent | f3fc10feb42930def6922fc050096ea38bafed7a (diff) | |
| download | podman-816e50ba02837946afade83e3cad06dd44d213ec.tar.gz podman-816e50ba02837946afade83e3cad06dd44d213ec.tar.bz2 podman-816e50ba02837946afade83e3cad06dd44d213ec.zip | |
podman-generate-systemd --new
Add a --new flag to podman-generate-systemd to create a new container
via podman-run instead of starting an existing container.
Creating a new container presents the challenge to find a reverse
mapping from a container to the CLI flags it can be created with. We
are doing this via `(Container).Config.CreateCommand` field, which
includes a copy of the process' command from procFS at creating time.
This field may not be useful when the container was not created via the
Podman CLI (e.g., via a Python script). Hence, we do not guarantee the
correctness of the generated files.
Signed-off-by: Valentin Rothberg <rothberg@redhat.com>
Diffstat (limited to 'docs/source/markdown')
| -rw-r--r-- | docs/source/markdown/podman-generate-systemd.1.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/docs/source/markdown/podman-generate-systemd.1.md b/docs/source/markdown/podman-generate-systemd.1.md index b81e68a46..4d3f9ba48 100644 --- a/docs/source/markdown/podman-generate-systemd.1.md +++ b/docs/source/markdown/podman-generate-systemd.1.md @@ -22,11 +22,16 @@ Generate files instead of printing to stdout. The generated files are named {co Use the name of the container for the start, stop, and description in the unit file +**--new** + +Create a new container via podman-run instead of starting an existing one. This option relies on container configuration files, which may not map directly to podman CLI flags; please review the generated output carefully before placing in production. + **--timeout**, **-t**=*value* Override the default stop timeout for the container with the given value. **--restart-policy**=*policy* + Set the systemd restart policy. The restart-policy must be one of: "no", "on-success", "on-failure", "on-abnormal", "on-watchdog", "on-abort", or "always". The default policy is *on-failure*. |