summaryrefslogtreecommitdiff
path: root/libpod/container_attach_unsupported.go
diff options
context:
space:
mode:
authorbaude <bbaude@redhat.com>2019-03-17 10:09:10 -0500
committerbaude <bbaude@redhat.com>2019-03-18 08:58:48 -0500
commit46f18764f205ead97fb5da70104951cf90bf5b6b (patch)
tree4f6512ae594ec9b475af29716afb9916428a7542 /libpod/container_attach_unsupported.go
parentea54a1c2f51d3173649277939738ce9b1c392076 (diff)
downloadpodman-46f18764f205ead97fb5da70104951cf90bf5b6b.tar.gz
podman-46f18764f205ead97fb5da70104951cf90bf5b6b.tar.bz2
podman-46f18764f205ead97fb5da70104951cf90bf5b6b.zip
podman logs on created container should exit
when running podman logs on a created container (which has no logs), podman should return gracefully (like docker) with a 0 return code. if multiple containers are provided and one is only in the created state (and no follow is used), we still display the logs for the other ids. fixes issue #2677 Signed-off-by: baude <bbaude@redhat.com>
Diffstat (limited to 'libpod/container_attach_unsupported.go')
0 files changed, 0 insertions, 0 deletions