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>
811 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.
--ip6=ipv6
Specify a static IPv6 address for the <<container|pod>>, for example fd46:db93:aa76:ac37::10. This option can only be used if the <<container|pod>> is joined to only a single network - i.e., --network=network-name is used at most once - and if the <<container|pod>> is not joining another container's network namespace via --network=container:id. The address must be within the network's IPv6 address pool.
To specify multiple static IPv6 addresses per <<container|pod>>, set multiple networks using the --network option with a static IPv6 address specified for each using the ip6 mode for that option.