1podman-network(1) General Commands Manual podman-network(1)
2
6 podman-network - Manage Podman networks
7
10 podman network subcommand
11
14 The network command manages networks for Podman.
15 Podman supports two network backends Netavark and CNI. Netavark is the
18 default network backend and was added in Podman version 4.0. CNI is
19 deprecated and will be removed in the next major Podman version 5.0, in
20 preference of Netavark. To configure the network backend use the net‐
21 work_backend key under the [Network] in containers.conf(5). New sys‐
22 tems use netavark by default, to check what backend is used run podman
23 info --format {{.Host.NetworkBackend}}.
24 All network commands work for both backends but CNI and Netavark use
27 different config files so networks have to be created again after a
28 backend change.
29
32 ┌───────────┬──────────────────────────────┬───────────────────────────────┐
33 │Command │ Man Page │ Description │
34 ├───────────┼──────────────────────────────┼───────────────────────────────┤
35 │connect │ podman-network-connect(1) │ Connect a container to a net‐ │
36 │ │ │ work │
37 ├───────────┼──────────────────────────────┼───────────────────────────────┤
38 │create │ podman-network-create(1) │ Create a Podman network │
39 ├───────────┼──────────────────────────────┼───────────────────────────────┤
40 │disconnect │ podman-network-disconnect(1) │ Disconnect a container from a │
41 │ │ │ network │
42 ├───────────┼──────────────────────────────┼───────────────────────────────┤
43 │exists │ podman-network-exists(1) │ Check if the given network │
44 │ │ │ exists │
45 ├───────────┼──────────────────────────────┼───────────────────────────────┤
46 │inspect │ podman-network-inspect(1) │ Display the network configu‐ │
47 │ │ │ ration for one or more net‐ │
48 │ │ │ works │
49 ├───────────┼──────────────────────────────┼───────────────────────────────┤
50 │ls │ podman-network-ls(1) │ Display a summary of networks │
51 ├───────────┼──────────────────────────────┼───────────────────────────────┤
52 │prune │ podman-network-prune(1) │ Remove all unused networks │
53 ├───────────┼──────────────────────────────┼───────────────────────────────┤
54 │reload │ podman-network-reload(1) │ Reload network configuration │
55 │ │ │ for containers │
56 ├───────────┼──────────────────────────────┼───────────────────────────────┤
57 │rm │ podman-network-rm(1) │ Remove one or more networks │
58 ├───────────┼──────────────────────────────┼───────────────────────────────┤
59 │update │ podman-network-update(1) │ Update an existing Podman │
60 │ │ │ network │
61 └───────────┴──────────────────────────────┴───────────────────────────────┘
62
64 Podman requires specific default IPs and, thus, network subnets. The
65 default values used by Podman can be modified in the containers.conf(5)
66 file.
67 Podman network
70 The default bridge network (called podman) uses 10.88.0.0/16 as a sub‐
71 net. When Podman runs as root, the podman network is used as default.
72 It is the same as adding the option --network bridge or --network pod‐
73 man. This subnet can be changed in containers.conf(5) under the [net‐
74 work] section. Set the default_subnet to any subnet that is free in the
75 environment. The name of the default network can also be changed from
76 podman to another name using the default network key. Note that this is
77 only done when no containers are running.
78 Slirp4netns
81 When Podman is run as rootless, the internet connectivity is provided
82 with slirp4netns by default. Slirp4nents uses 10.0.2.0/24 for its de‐
83 fault network. This can also be changed in containers.conf(5) but under
84 the [engine] section. Use the network_cmd_options key and add
85 ["cidr=X.X.X.X/24"] as a value. Note that slirp4netns needs a network
86 prefix size between 1 and 25. This option accepts an array, so more op‐
87 tions can be added in a comma-separated string as described on the pod‐
88 man-network-create(1) man page. To change the CIDR for just one con‐
89 tainer, specify it on the cli using the --network option like this:
90 --network slirp4netns:cidr=192.168.1.0/24.
91 When using the default network as rootless, i.e. --network pod‐
94 man/bridge, then it also uses the same subnet as described above in ad‐
95 dition to the slirp4netns subnet.
96 Podman network create
99 When a new network is created with a podman network create command, and
100 no subnet is given with the --subnet option, Podman starts picking a
101 free subnet from 10.89.0.0/24 to 10.255.255.0/24. Use the default_sub‐
102 net_pools option under the [network] section in containers.conf(5) to
103 change the range and/or size that is assigned by default.
104
107 podman(1), podman-network-create(1), containers.conf(5)
108 podman-network(1)