diff options
| author | Matthew Heon <mheon@redhat.com> | 2020-10-29 16:34:03 -0400 |
|---|---|---|
| committer | Matthew Heon <mheon@redhat.com> | 2020-10-30 09:23:47 -0400 |
| commit | ed9edf840adbc159fb3ddc99638b3111440c8cfe (patch) | |
| tree | f329dee3fd536dae5b80c9bac19df5af83bc2eb6 /cmd/podman/system/migrate.go | |
| parent | 4d87306fbe06674b16f188fea187282f29c0dc58 (diff) | |
| download | podman-ed9edf840adbc159fb3ddc99638b3111440c8cfe.tar.gz podman-ed9edf840adbc159fb3ddc99638b3111440c8cfe.tar.bz2 podman-ed9edf840adbc159fb3ddc99638b3111440c8cfe.zip | |
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>
Diffstat (limited to 'cmd/podman/system/migrate.go')
0 files changed, 0 insertions, 0 deletions