summaryrefslogtreecommitdiff
path: root/docs/links/podman-image-build.1
diff options
context:
space:
mode:
authorMatthew Heon <mheon@redhat.com>2019-02-11 12:57:08 -0500
committerMatthew Heon <mheon@redhat.com>2019-02-12 10:14:57 -0500
commitb6775d5d22d463e4d92d6358ccd48dab6f8a1862 (patch)
treea0c0373125736b8b9bf59c93a794c7cadadd05c2 /docs/links/podman-image-build.1
parentbdf537f4fc983c30c945297d9ee33891a127f9bd (diff)
downloadpodman-b6775d5d22d463e4d92d6358ccd48dab6f8a1862.tar.gz
podman-b6775d5d22d463e4d92d6358ccd48dab6f8a1862.tar.bz2
podman-b6775d5d22d463e4d92d6358ccd48dab6f8a1862.zip
Fix manual detach from containers to not wait for exit
At present, when manually detaching from an attached container (using the detach hotkeys, default C-p C-q), Podman will still wait for the container to exit to obtain its exit code (so we can set Podman's exit code to match). This is correct in the case where attach finished because the container exited, but very wrong for the manual detach case. As a result of this, we can no longer guarantee that the cleanup and --rm functions will fire at the end of 'podman run' - we may be exiting before we get that far. Cleanup is easy enough - we swap to unconditionally using the cleanup processes we've used for detached and rootless containers all along. To duplicate --rm we need to also teach 'podman cleanup' to optionally remove containers instead of cleaning them up. (There is an argument for just using 'podman rm' instead of 'podman cleanup --rm', but cleanup does have different semantics given that we only ever expect it to run when the container has just exited. I think it might be useful to keep the two separate for things like 'podman events'...) Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'docs/links/podman-image-build.1')
0 files changed, 0 insertions, 0 deletions