mirror of
https://github.com/containers/podman.git
synced 2025-06-09 17:07:51 +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>
789 B
789 B
####> This option file is used in: ####> podman create, pod create, run ####> If you edit this file, make sure your changes ####> are applicable to all of those.
--network-alias=alias
Add a network-scoped alias for the <<container|pod>>, setting the alias for all networks that the container joins. To set a
name only for a specific network, use the alias option as described under the --network option.
If the network has DNS enabled (podman network inspect -f {{.DNSEnabled}} <name>),
these aliases can be used for name resolution on the given network. This option can be specified multiple times.
NOTE: When using CNI a <<container|pod>> will only have access to aliases on the first network that it joins. This limitation does
not exist with netavark/aardvark-dns.