mirror of
https://github.com/containers/podman.git
synced 2025-06-03 20:33:20 +08:00
34d412e13d
command tables are chock full of duplication, hence they break.
Look for inconsistencies between the displayed man page name
and the actual man page name:
| foo | [podman-foo(1)](podman-cmd-foo.1.md) | ...
^^^
Inspired by #17474.
We can't actually check the subcommand name (the plain "foo")
because there are many existing subcommands whose name does
not match the man page: rmi vs image-rm, list vs podman-ps.
Signed-off-by: Ed Santiago <santiago@redhat.com>
40 lines
2.7 KiB
Markdown
40 lines
2.7 KiB
Markdown
% podman-network 1
|
|
|
|
## NAME
|
|
podman\-network - Manage Podman networks
|
|
|
|
## SYNOPSIS
|
|
**podman network** *subcommand*
|
|
|
|
## DESCRIPTION
|
|
The network command manages networks for Podman.
|
|
|
|
Podman supports two network backends [Netavark](https://github.com/containers/netavark)
|
|
and [CNI](https://www.cni.dev/). Netavark is the default network backend and was added in Podman v4.0. CNI will be
|
|
deprecated in the future in preference of Netavark. To configure
|
|
the network backend use the `network_backend`key under the `[Network]` in
|
|
**[containers.conf(5)](https://github.com/containers/common/blob/main/docs/containers.conf.5.md)**.
|
|
New systems should use netavark by default, to check what backed is used run
|
|
`podman info --format {{.Host.NetworkBackend}}`.
|
|
|
|
All network commands work for both backends but CNI and Netavark use different config files
|
|
so networks have to be created again after a backend change.
|
|
|
|
## COMMANDS
|
|
|
|
| Command | Man Page | Description |
|
|
| ---------- | -------------------------------------------------------------- | --------------------------------------------------------------- |
|
|
| connect | [podman-network-connect(1)](podman-network-connect.1.md) | Connect a container to a network |
|
|
| create | [podman-network-create(1)](podman-network-create.1.md) | Create a Podman network |
|
|
| disconnect | [podman-network-disconnect(1)](podman-network-disconnect.1.md) | Disconnect a container from a network |
|
|
| exists | [podman-network-exists(1)](podman-network-exists.1.md) | Check if the given network exists |
|
|
| inspect | [podman-network-inspect(1)](podman-network-inspect.1.md) | Displays the network configuration for one or more networks |
|
|
| ls | [podman-network-ls(1)](podman-network-ls.1.md) | Display a summary of networks |
|
|
| prune | [podman-network-prune(1)](podman-network-prune.1.md) | Remove all unused networks |
|
|
| reload | [podman-network-reload(1)](podman-network-reload.1.md) | Reload network configuration for containers |
|
|
| rm | [podman-network-rm(1)](podman-network-rm.1.md) | Remove one or more networks |
|
|
| update | [podman-network-update(1)](podman-network-update.1.md) | Update an existing Podman network |
|
|
|
|
## SEE ALSO
|
|
**[podman(1)](podman.1.md)**, **[containers.conf(5)](https://github.com/containers/common/blob/main/docs/containers.conf.5.md)**
|