-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
RFE: let logs command accept multiple containers #2219
Comments
can you provide an example of what you'd be thinking? like would the containerid precede the log message? |
Yes, that's how docker-compose works. I would expect the same/similar functionality:
|
I don't think this is a bad idea, we could even do --all. Please open a PR if you have something working? |
I'll try to take a look and figure it out. |
@TomasTomecek Have you done anything on this? |
I haven't found free time to work on this. Sadly that will likely not change in coming weeks. This issue is still on my mind, though. |
@TomasTomecek what are the particulars around this? are you thinking of being able to add multiple container ids? what about --all ? one issue for me with all is that it might be too hard to be able to watch for containers that start, stop, rm, etc? |
yes
I don't follow, logs command doesn't have such option now.
Yes, that's correct. Therefore I'd do the initial implementation by only accepting started containers and if a container dies, just remove it from the watch list. |
i have a working version of this. let me clean it up and perhaps @TomasTomecek could give it a test? |
add the ability for users to specify more than one container at a time while using podman logs. If more than one container is being displayed, podman will also prepend a shortened container id of the container on the log line. also, enabled the podman-remote logs command during the refactoring of the above ability. fixes issue containers#2219 Signed-off-by: baude <bbaude@redhat.com>
This issue is resolved. |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
I'm trying to migrate my projects from docker-compose to a podman-based solution. Probably the main blocker for me is that in docker-compose, you would get a stream of logs from all the containers. In podman, I can only pass a single container to
podman logs
.Do you think this is a good idea?
I already checked out the code and I think it should be doable.
The text was updated successfully, but these errors were encountered: