60 lines
1.7 KiB
Groff
60 lines
1.7 KiB
Groff
.nh
|
|
.TH podman-network-reload 1
|
|
.SH NAME
|
|
podman-network-reload \- Reload network configuration for containers
|
|
|
|
.SH SYNOPSIS
|
|
\fBpodman network reload\fP [\fIoptions\fP] [\fIcontainer...\fP]
|
|
|
|
.SH DESCRIPTION
|
|
Reload one or more container network configurations.
|
|
|
|
.PP
|
|
Rootful Podman relies on iptables rules in order to provide network connectivity. If the iptables rules are deleted,
|
|
this happens for example with \fBfirewall-cmd --reload\fR, the container loses network connectivity. This command restores
|
|
the network connectivity.
|
|
|
|
.SH OPTIONS
|
|
.SS \fB--all\fP, \fB-a\fP
|
|
Reload network configuration of all containers.
|
|
|
|
.SS \fB--latest\fP, \fB-l\fP
|
|
Instead of providing the container name or ID, use the last created container.
|
|
Note: the last started container can be from other users of Podman on the host machine.
|
|
(This option is not available with the remote Podman client, including Mac and Windows
|
|
(excluding WSL2) machines)
|
|
|
|
.SH EXAMPLE
|
|
Reload the network configuration after a firewall reload:
|
|
|
|
.EX
|
|
# podman run -p 80:80 -d nginx
|
|
b1b538e8bc4078fc3ee1c95b666ebc7449b9a97bacd15bcbe464a29e1be59c1c
|
|
# curl 127.0.0.1
|
|
works
|
|
# sudo firewall-cmd --reload
|
|
success
|
|
# curl 127.0.0.1
|
|
hangs
|
|
# podman network reload b1b538e8bc40
|
|
b1b538e8bc4078fc3ee1c95b666ebc7449b9a97bacd15bcbe464a29e1be59c1c
|
|
# curl 127.0.0.1
|
|
works
|
|
.EE
|
|
|
|
.PP
|
|
Reload the network configuration for all containers:
|
|
|
|
.EX
|
|
# podman network reload --all
|
|
b1b538e8bc4078fc3ee1c95b666ebc7449b9a97bacd15bcbe464a29e1be59c1c
|
|
fe7e8eca56f844ec33af10f0aa3b31b44a172776e3277b9550a623ed5d96e72b
|
|
.EE
|
|
|
|
.SH SEE ALSO
|
|
\fBpodman(1)\fP, \fBpodman-network(1)\fP
|
|
|
|
.SH HISTORY
|
|
December 2020, Originally compiled by Paul Holzinger paul.holzinger@web.de
|
|
\[la]mailto:paul.holzinger@web.de\[ra]
|