mirror of
https://github.com/containers/podman.git
synced 2026-07-10 23:35:04 -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>
23 lines
993 B
Markdown
23 lines
993 B
Markdown
####> This option file is used in:
|
|
####> podman podman-container.unit.5.md.in, create, run
|
|
####> If file is edited, make sure the changes
|
|
####> are applicable to all of those.
|
|
<< if is_quadlet >>
|
|
### `Entrypoint="command"`
|
|
<< else >>
|
|
#### **--entrypoint**=*"command"* | *'["command", "arg1", ...]'*
|
|
<< endif >>
|
|
|
|
Override the default ENTRYPOINT from the image.
|
|
|
|
The ENTRYPOINT of an image is similar to a COMMAND
|
|
because it specifies what executable to run when the container starts, but it is
|
|
(purposely) more difficult to override. The ENTRYPOINT gives a container its
|
|
default nature or behavior. When the ENTRYPOINT is set, the
|
|
container runs as if it were that binary, complete with default options. More options can be
|
|
passed in via the COMMAND. But, if a user wants to run
|
|
something else inside the container, the << '**Entrypoint=**' if is_quadlet else '**--entrypoint=**' >> option allows a new
|
|
ENTRYPOINT to be specified.
|
|
|
|
Specify multi option commands in the form of a JSON string.
|