summaryrefslogtreecommitdiff
path: root/libpod
diff options
context:
space:
mode:
authorMatthew Heon <mheon@redhat.com>2022-04-13 14:04:05 -0400
committerMatthew Heon <mheon@redhat.com>2022-04-13 14:04:05 -0400
commit02b7eeff62224333a6ec768998a6b5db8cd7dc4d (patch)
tree59a4090d2b1cf44e05ba91c6c77a25091aa93ade /libpod
parentf6ce14b066ad57a86642f22c15ac42020fc0f660 (diff)
downloadpodman-02b7eeff62224333a6ec768998a6b5db8cd7dc4d.tar.gz
podman-02b7eeff62224333a6ec768998a6b5db8cd7dc4d.tar.bz2
podman-02b7eeff62224333a6ec768998a6b5db8cd7dc4d.zip
Allow HTTP attach to stopped containers
There's a potential race condition where we attempt to attach to a container immediately after it's been stopped, but before the cleanup process has run on it. The existing code doesn't allow an attach to containers in the Stopped state (cleanup process has not run) but does allow an attach to containers in the Exited state (cleanup process has run). This doesn't make very much sense and there's no technical reason to restrict attach to only Exited containers, so allow attaching to Stopped containers. [NO NEW TESTS NEEDED] Testing this is very racy - we need to get in before the cleanup process runs, which isn't really deterministic when we're invoked from a script - like the CI tests. Signed-off-by: Matthew Heon <mheon@redhat.com>
Diffstat (limited to 'libpod')
0 files changed, 0 insertions, 0 deletions