'\" t
.nh
.TH podman-network 1
.SH NAME
podman-network \- Manage Podman networks

.SH SYNOPSIS
\fBpodman network\fP \fIsubcommand\fP

.SH DESCRIPTION
The network command manages networks for Podman.

.PP
Podman uses Netavark as the network backend.

.SH DNS NOTES
On networks with DNS enabled (the default, unless \fB--disable-dns\fP is used),
aardvark-dns registers each
container under its name and aliases. Containers that share a pod network
namespace are registered under the pod name.

.PP
The container name is always registered. The short container ID (first 12
characters) is always registered as an alias. When \fB--hostname\fP is explicitly
set, that hostname is also registered as an alias. By default the hostname
inside the container is the short ID, so it already matches the alias. Setting
\fIcontainer_name_as_hostname=true\fP in the \fB[containers]\fR section of
\fBcontainers.conf(5)\fP
changes the hostname only; DNS entries remain unchanged. Additional names can be set with the \fBalias=\fP option
in \fB--network\fP (e.g., \fBpodman run --network mynet:alias=foo\fP),
with \fB--network-alias\fP, or with \fB--alias\fP on \fBpodman network connect\fP\&.
Auto-generated names use an underscore between words, for example \fBexciting_chebyshev\fR\&.

.SH COMMANDS
.TS
allbox;
l l l 
l l l .
\fBCommand\fP	\fBMan Page\fP	\fBDescription\fP
connect	podman-network-connect(1)	T{
Connect a container to a network
T}
create	podman-network-create(1)	Create a Podman network
disconnect	podman-network-disconnect(1)	T{
Disconnect a container from a network
T}
exists	podman-network-exists(1)	T{
Check if the given network exists
T}
inspect	podman-network-inspect(1)	T{
Display the network configuration for one or more networks
T}
ls	podman-network-ls(1)	Display a summary of networks
prune	podman-network-prune(1)	Remove all unused networks
reload	podman-network-reload(1)	T{
Reload network configuration for containers
T}
rm	podman-network-rm(1)	Remove one or more networks
update	podman-network-update(1)	T{
Update an existing Podman network
T}
.TE

.SH SUBNET NOTES
Podman requires specific default IPs and, thus, network subnets.  The default values used by Podman can be modified in the \fBcontainers.conf(5)\fP file.

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

.SS Pasta
Pasta by default performs no Network Address Translation (NAT) and copies the IPs from your main interface into the container namespace. If pasta cannot find an interface with the default route, it will select an interface if there is only one interface with a valid route. If you do not have a default route and several interfaces have defined routes, pasta will be unable to figure out the correct interface and it will fail to start. To specify the interface, use \fB-i\fR option to pasta. A default set of pasta options can be set in \fBcontainers.conf(5)\fP under the \fB[network]\fR section with the \fBpasta_options\fR key.

.PP
Pasta is the default rootless networking tool.

.SS Podman network create
When a new network is created with a \fBpodman network create\fR command, and no subnet is given with the --subnet option, Podman starts picking a free subnet from 10.89.0.0/24 to 10.255.255.0/24. Use the \fBdefault_subnet_pools\fR option under the \fB[network]\fR section in \fBcontainers.conf(5)\fP to change the range and/or size that is assigned by default.

.SH SEE ALSO
\fBpodman(1)\fP, \fBpodman-network-create(1)\fP, \fBcontainers.conf(5)\fP