-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
podman pod logs enhancements: when to exit #13268
Comments
we might be able to create systemd for an entire stack, discussion here
and any suggestion to make it Type=simple or forking instead of Type=oneshot |
podman pod create does not start the pod so podman logs will exit immediately because no containers are running. I think you have to run podman pod create followed by podman pod start. |
I need to start following before starting so that I won't miss the logs in-between
|
Ah I see because you have a pod without infra container it does not work. |
yes, I'm attaching a stack of containers for example wordpress stack (wordpress php-fpm, nginx, memcached, mysql) or awx stack
each of them have different mounts, hostname, userns stack, ...etc. I create the pod later stop the pod and start it I hope if there is a flag to tell |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
@muayyad-alsadi @Luap99 where are we on this issue? Does it still exists, or did you find a workaround? |
A friendly reminder that this issue had no activity for 30 days. |
A friendly reminder that this issue had no activity for 30 days. |
Since I have never heard back, I am going to guess this is no longer needed and close. Reopen if I am mistaken. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
a way specify for
podman pod logs -f
for example
--exit-code-from <MY_CNT>
and--exit-with-container=all | any | <CNT1,CNT2>
this might help creating a simpler systemd unit for multi-container pod
Steps to reproduce the issue:
and then on another screen
Describe the results you received:
podman pod logs --tail=100 -f pod_testlogs
exits instantly if run afterpodman pod create --name=pod_testlogs
Describe the results you expected:
it should have a way to ask it wait containers to join
related to
#13261
The text was updated successfully, but these errors were encountered: