Paul Holzinger 3215d5124f podman-remote run: improve how we get the exit code ...

Call the wait endpoint right away when a container is started and not
only when attach is done, this allows us for wait to work when the
container has been removed otherwise (i.e. podman-remote run --rm). In
that case it was possible that wait failed and we then fall back to
reading events. However based on some reports there seems to be the
chance that the event readin is not working for them either and returns
a bad error "Cannot get exit code: <nil>" which does not help anybody.

Signed-off-by: Paul Holzinger <pholzing@redhat.com>

2024-10-08 18:03:11 +02:00

..

entities

Add --health-max-log-count, --health-max-log-size, --health-log-destination flags

2024-09-25 14:01:35 +02:00

filters

Replace golang.org/x/exp/slices with slices from std

2024-04-23 11:16:40 +02:00

infra

podman-remote run: improve how we get the exit code

2024-10-08 18:03:11 +02:00

utils

Merge pull request #21583 from Luap99/scp-port

2024-02-12 21:35:56 +00:00