Matthew Heon ed9edf840a When container stops, drop sig-proxy errors to infos ... The sig-proxy code is set up to error on failing to forward signals to a container. This is reasonable in cases where the container is running, but something strange went wrong - but when the Kill fails because the container is stopped, we shouldn't bother with aggressive Error logging since this is an expected part of the container lifecycle - it stops, and then `podman run` also stops, but there is a timing window in between where signals will fail to be proxied, and we should not print angry errors during that. Signed-off-by: Matthew Heon <mheon@redhat.com>		2020-10-30 09:23:47 -04:00
..
sigproxy_linux.go	When container stops, drop sig-proxy errors to infos	2020-10-30 09:23:47 -04:00
terminal.go	update github.com/docker/docker and relevant deps	2020-09-18 02:22:25 +09:00
terminal_linux.go	Switch all references to github.com/containers/libpod -> podman	2020-07-28 08:23:45 -04:00