I opened https://github.com/containers/podman/issues/10596 for this now. On 6/8/21 8:42 AM, Valentin Rothberg wrote:
Hi Hendrik,
Thanks for reaching out.
On Tue, Jun 8, 2021 at 12:25 AM Hendrik Haddorp <hendrik.haddorp@gmx.net <mailto:hendrik.haddorp@gmx.net>> wrote:
Hi,
I have a test service that does a slow graceful shutdown and logs a few things while doing so. If I run "podman logs -f <name>" for the container the logs stop as soon as the container receives the SIGTERM signal, so once it enters the "stopping" state. Consequently the terminal containing the "podman run ..." command shows more logs then the "podman logs -f" command. Shouldn't "podman logs -f" follow the logs until the container reached the stopped state and the streams got closed and not only until it starts its shutdown?
Yes it should. Could you open an issue on github.com/containers/podman <http://github.com/containers/podman>, ideally with a reproducer? We recently fixed a number of issues in the journald log driver but I assume you're using the k8s-file driver?
Kind regards, Valentin
regards, Hendrik _______________________________________________ Podman mailing list -- podman@lists.podman.io <mailto:podman@lists.podman.io> To unsubscribe send an email to podman-leave@lists.podman.io <mailto:podman-leave@lists.podman.io>
_______________________________________________ Podman mailing list -- podman@lists.podman.io To unsubscribe send an email to podman-leave@lists.podman.io