1podman-network-reload(1)() podman-network-reload(1)()
2
3
4
6 podman-network-reload - Reload network configuration for containers
7
8
10 podman network reload [options] [container...]
11
12
14 Reload one or more container network configurations.
15
16
17 Rootful Podman relies on iptables rules in order to provide network
18 connectivity. If the iptables rules are deleted, this happens for exam‐
19 ple with firewall-cmd --reload, the container loses network connectiv‐
20 ity. This command restores the network connectivity.
21
22
23 This command is not available for rootless users since rootless con‐
24 tainers are not affected by such connectivity problems.
25
26
28 --all, -a
29 Reload network configuration of all containers.
30
31
32 --latest, -l
33 Instead of providing the container name or ID, use the last created
34 container. If you use methods other than Podman to run containers such
35 as CRI-O, the last started container could be from either of those
36 methods.
37
38
39 The latest option is not supported on the remote client.
40
41
43 Reload the network configuration after a firewall reload.
44
45
46 # podman run -p 80:80 -d nginx
47 b1b538e8bc4078fc3ee1c95b666ebc7449b9a97bacd15bcbe464a29e1be59c1c
48 # curl 127.0.0.1
49 works
50 # sudo firewall-cmd --reload
51 success
52 # curl 127.0.0.1
53 hangs
54 # podman network reload b1b538e8bc40
55 b1b538e8bc4078fc3ee1c95b666ebc7449b9a97bacd15bcbe464a29e1be59c1c
56 # curl 127.0.0.1
57 works
58
59
60
61 Reload the network configuration for all containers.
62
63
64 # podman network reload --all
65 b1b538e8bc4078fc3ee1c95b666ebc7449b9a97bacd15bcbe464a29e1be59c1c
66 fe7e8eca56f844ec33af10f0aa3b31b44a172776e3277b9550a623ed5d96e72b
67
68
69
71 podman(1), podman-network(1)
72
73
75 December 2020, Originally compiled by Paul Holzinger
76 paul.holzinger@web.de ⟨mailto:paul.holzinger@web.de⟩
77
78
79
80 podman-network-reload(1)()