diff options
| author | Matthew Heon <mheon@redhat.com> | 2021-10-06 09:25:24 -0400 |
|---|---|---|
| committer | Matthew Heon <mheon@redhat.com> | 2021-10-06 11:19:32 -0400 |
| commit | e1089e89d7b8f5204ccb226934e46df736af4925 (patch) | |
| tree | d9e71b0d38968d6f0487694f266ae3db9568945a /RELEASE_NOTES.md | |
| parent | 8bcc086b1b9d8aa0ef3bb08d37542adf9de26ac5 (diff) | |
| download | podman-e1089e89d7b8f5204ccb226934e46df736af4925.tar.gz podman-e1089e89d7b8f5204ccb226934e46df736af4925.tar.bz2 podman-e1089e89d7b8f5204ccb226934e46df736af4925.zip | |
Allow `podman stop` to be run on Stopping containers
This allows you to stop a container after a `podman stop` process
started, but did not finish, stopping the container (probably an
ignored stop signal, with no time to SIGKILL?). This is a very
narrow case, but once you're in it the only way to recover is a
`podman rm -f` of the container or extensive manual remediation
(you'd have to kill the container yourself, manually, and then
force a `podman ps --all --sync` to update its status from the
OCI runtime).
[NO NEW TESTS NEEDED] I have no idea how to verify this one -
we need to test that it actually started *during* the other stop
command, and that's nontrivial.
Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'RELEASE_NOTES.md')
0 files changed, 0 insertions, 0 deletions