mirror of
https://github.com/podman-container-tools/podman.git
synced 2026-08-19 23:07:52 +00:00
b0286d6b43
This adds a new command, 'podman network reload', to reload the networks of existing containers, forcing recreation of firewall rules after e.g. `firewall-cmd --reload` wipes them out. Under the hood, this works by calling CNI to tear down the existing network, then recreate it using identical settings. We request that CNI preserve the old IP and MAC address in most cases (where the container only had 1 IP/MAC), but there will be some downtime inherent to the teardown/bring-up approach. The architecture of CNI doesn't really make doing this without downtime easy (or maybe even possible...). At present, this only works for root Podman, and only locally. I don't think there is much of a point to adding remote support (this is very much a local debugging command), but I think adding rootless support (to kill/recreate slirp4netns) could be valuable. Signed-off-by: Matthew Heon <matthew.heon@pm.me> Signed-off-by: Paul Holzinger <paul.holzinger@web.de> |
||
|---|---|---|
| .. | ||
| annotations | ||
| api | ||
| auth | ||
| autoupdate | ||
| bindings | ||
| cgroups | ||
| channel | ||
| checkpoint | ||
| criu | ||
| ctime | ||
| domain | ||
| env | ||
| errorhandling | ||
| hooks | ||
| inspect | ||
| kubeutils | ||
| lookup | ||
| namespaces | ||
| netns | ||
| parallel | ||
| ps | ||
| registrar | ||
| registries | ||
| resolvconf | ||
| rootless | ||
| rootlessport | ||
| seccomp | ||
| selinux | ||
| signal | ||
| specgen | ||
| systemd | ||
| terminal | ||
| timetype | ||
| tracing | ||
| trust | ||
| util | ||