github.com/hanks177/podman/v4@v4.1.3-0.20220613032544-16d90015bc83/docs/source/markdown/podman-network-reload.1.md (about) 1 % podman-network-reload(1) 2 3 ## NAME 4 podman\-network\-reload - Reload network configuration for containers 5 6 ## SYNOPSIS 7 **podman network reload** [*options*] [*container...*] 8 9 ## DESCRIPTION 10 Reload one or more container network configurations. 11 12 Rootful Podman relies on iptables rules in order to provide network connectivity. If the iptables rules are deleted, 13 this happens for example with `firewall-cmd --reload`, the container loses network connectivity. This command restores 14 the network connectivity. 15 16 ## OPTIONS 17 #### **--all**, **-a** 18 19 Reload network configuration of all containers. 20 21 #### **--latest**, **-l** 22 23 Instead of providing the container name or ID, use the last created container. If you use methods other than Podman 24 to run containers such as CRI-O, the last started container could be from either of those methods. (This option is not available with the remote Podman client, including Mac and Windows (excluding WSL2) machines) 25 26 ## EXAMPLE 27 28 Reload the network configuration after a firewall reload. 29 30 ``` 31 # podman run -p 80:80 -d nginx 32 b1b538e8bc4078fc3ee1c95b666ebc7449b9a97bacd15bcbe464a29e1be59c1c 33 # curl 127.0.0.1 34 works 35 # sudo firewall-cmd --reload 36 success 37 # curl 127.0.0.1 38 hangs 39 # podman network reload b1b538e8bc40 40 b1b538e8bc4078fc3ee1c95b666ebc7449b9a97bacd15bcbe464a29e1be59c1c 41 # curl 127.0.0.1 42 works 43 ``` 44 45 Reload the network configuration for all containers. 46 47 ``` 48 # podman network reload --all 49 b1b538e8bc4078fc3ee1c95b666ebc7449b9a97bacd15bcbe464a29e1be59c1c 50 fe7e8eca56f844ec33af10f0aa3b31b44a172776e3277b9550a623ed5d96e72b 51 ``` 52 53 54 ## SEE ALSO 55 **[podman(1)](podman.1.md)**, **[podman-network(1)](podman-network.1.md)** 56 57 ## HISTORY 58 December 2020, Originally compiled by Paul Holzinger <paul.holzinger@web.de>