mirror of
https://github.com/containers/podman.git
synced 2026-03-29 12:03:29 -04:00
7ebb95a3bf
Removed all CNI-specific documentation from man pages: - podman.1.md: Simplified --network-config-dir to only mention netavark directories - podman-network.1.md: Removed dual backend description, now states netavark is the only backend - podman-network-create.1.md: Removed CNI-specific notes about DNS and DHCP socket configuration - podman-network-connect.1.md: Removed CNI limitation note about network aliases - options/network-alias.md: Removed CNI limitation note about network aliases - podman-info.1.md: Updated example output to show netavark backend information instead of CNI All man pages now reflect netavark as the sole network backend. Signed-off-by: Lokesh Mandvekar <lsm5@redhat.com>
11 lines
615 B
Markdown
11 lines
615 B
Markdown
####> This option file is used in:
|
|
####> podman create, pod create, run
|
|
####> If file is edited, make sure the 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.
|