mirror of
https://github.com/containers/podman.git
synced 2025-07-29 11:22:38 +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>
22 lines
1.0 KiB
Markdown
22 lines
1.0 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.
|
|
#### **--entrypoint**=*"command"* | *'["command", "arg1", ...]'*
|
|
|
|
Overwrite the default ENTRYPOINT of the image.
|
|
|
|
This option allows you to overwrite the default entrypoint of 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, so that when you set an ENTRYPOINT you can run the
|
|
container as if it were that binary, complete with default options, and you can
|
|
pass in more options via the COMMAND. But, sometimes an operator may want to run
|
|
something else inside the container, so you can override the default ENTRYPOINT
|
|
at runtime by using a **--entrypoint** and a string to specify the new
|
|
ENTRYPOINT.
|
|
|
|
You need to specify multi option commands in the form of a json string.
|