mirror of
https://github.com/containers/podman.git
synced 2026-05-31 03:46:12 -04:00
7612af4c0e
This commit does the following: - Splits the podman-systemd.unit.5.md into multiple files - one for each quadlet file type. - Adds the podman-quadlet-basic-usage.7.md for quadlet examples. - Majority of the text in the new files is copied from the podman-systemd.unit.5.md - Adds support for very simple condditional in the markdown_preprocess. - Uses new logic in markdown_preprocess in options/*.md to use a single .md file for both podman subcommands man-pages and quadlet man-pages. This deduplicates the Quadlet man-pages a lot. - Adds new `@@option quadlet:source.md`` preprocess command to import such .md files from options directory. Signed-off-by: Jan Kaluza <jkaluza@redhat.com>
19 lines
1.1 KiB
Markdown
19 lines
1.1 KiB
Markdown
####> This option file is used in:
|
|
####> podman podman-container.unit.5.md.in
|
|
####> If file is edited, make sure the changes
|
|
####> are applicable to all of those.
|
|
### `Exec=command`
|
|
|
|
Additional arguments for the container; this has exactly the same effect as passing
|
|
more arguments after a `podman run <image> <arguments>` invocation.
|
|
|
|
The format is the same as for [systemd command lines](https://www.freedesktop.org/software/systemd/man/systemd.service.html#Command%20lines),
|
|
However, unlike the similarly named systemd `ExecStart=` directive
|
|
which operates on the ambient root filesystem, it is very common for container
|
|
images to have their own `ENTRYPOINT` or `CMD` metadata which this interacts with.
|
|
|
|
The default expectation for many images is that the image will include an `ENTRYPOINT`
|
|
with a default binary, and this field will add arguments to that entrypoint.
|
|
|
|
Another way to describe this is that it works the same way as the [args field in a Kubernetes pod](https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#running-a-command-in-a-shell).
|