diff options
| author | Matthew Heon <matthew.heon@pm.me> | 2019-09-23 14:54:10 -0400 |
|---|---|---|
| committer | Matthew Heon <matthew.heon@pm.me> | 2019-09-24 09:52:11 -0400 |
| commit | b57d2f4cc7bb26e8bd2ec4cf4eb66f739ed3beb4 (patch) | |
| tree | 4d0c22a5d8977b330c7431c72bd53899ff6f07e7 /cmd/podman/unpause.go | |
| parent | c0eff1a81c2718498aa8e75f7e45bfb688c91482 (diff) | |
| download | podman-b57d2f4cc7bb26e8bd2ec4cf4eb66f739ed3beb4.tar.gz podman-b57d2f4cc7bb26e8bd2ec4cf4eb66f739ed3beb4.tar.bz2 podman-b57d2f4cc7bb26e8bd2ec4cf4eb66f739ed3beb4.zip | |
Force a CNI Delete on refreshing containers
CNI expects that a DELETE be run before re-creating container
networks. If a reboot occurs quickly enough that containers can't
stop and clean up, that DELETE never happens, and Podman
currently wipes the old network info and thinks the state has
been entirely cleared. Unfortunately, that may not be the case on
the CNI side. Some things - like IP address reservations - may
not have been cleared.
To solve this, manually re-run CNI Delete on refresh. If the
container has already been deleted this seems harmless. If not,
it should clear lingering state.
Fixes: #3759
Signed-off-by: Matthew Heon <matthew.heon@pm.me>
Diffstat (limited to 'cmd/podman/unpause.go')
0 files changed, 0 insertions, 0 deletions