Your company here — click to reach over 10,000 unique daily visitors

podman-network - Man Page

Manage Podman networks


podman network subcommand


The network command manages networks for Podman.

Podman supports two network backends Netavark and CNI. Netavark is the default network backend and was added in Podman version 4.0. CNI is deprecated and will be removed in the next major Podman version 5.0, in preference of Netavark. To configure the network backend use the network_backend key under the [Network] in containers.conf(5). New systems use netavark by default, to check what backend 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.


CommandMan PageDescription
connectpodman-network-connect(1)Connect a container to a network
createpodman-network-create(1)Create a Podman network
disconnectpodman-network-disconnect(1)Disconnect a container from a network
existspodman-network-exists(1)Check if the given network exists
inspectpodman-network-inspect(1)Display the network configuration for one or more networks
lspodman-network-ls(1)Display a summary of networks
prunepodman-network-prune(1)Remove all unused networks
reloadpodman-network-reload(1)Reload network configuration for containers
rmpodman-network-rm(1)Remove one or more networks
updatepodman-network-update(1)Update an existing Podman network

Subnet Notes

Podman requires specific default IPs and, thus, network subnets.  The default values used by Podman can be modified in the containers.conf(5) file.

Podman network

The default bridge network (called podman) uses as a subnet. When Podman runs as root, the podman network is used as default.  It is the same as adding the option --network bridge or --network podman. This subnet can be changed in containers.conf(5) under the [network] section. Set the default_subnet to any subnet that is free in the environment. The name of the default network can also be changed from podman to another name using the default network key. Note that this is only done when no containers are running.


When Podman is run as rootless, the internet connectivity is provided with slirp4netns by default. Slirp4nents uses for its default network. This can also be changed in containers.conf(5) but under the [engine] section. Use the network_cmd_options key and add ["cidr=X.X.X.X/24"] as a value. Note that slirp4netns needs a network prefix size between 1 and 25. This option accepts an array, so more options can be added in a comma-separated string as described on the podman-network-create(1) man page. To change the CIDR for just one container, specify it on the cli using the --network option like this: --network slirp4netns:cidr=

When using the default network as rootless, i.e. --network podman/bridge, then it also uses the same subnet as described above in addition to the slirp4netns subnet.

Podman network create

When a new network is created with a podman network create command, and no subnet is given with the --subnet option, Podman starts picking a free subnet from to Use the default_subnet_pools option under the [network] section in containers.conf(5) to change the range and/or size that is assigned by default.

See Also

podman(1), podman-network-create(1), containers.conf(5)

Referenced By

podman(1), podman-network-connect(1), podman-network-create(1), podman-network-disconnect(1), podman-network-exists(1), podman-network-inspect(1), podman-network-ls(1), podman-network-prune(1), podman-network-reload(1), podman-network-rm(1), podman-network-update(1).

The man page docker-network(1) is an alias of podman-network(1).