You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The recently added "Logs" tab is great! Would it be possible to make it automatically refresh or "follow" the logs? Alternatively, a refresh button could also work. I can use podman-compose logs -f <container> to follow the logs, but Pods doesn't update alongside with new output; even restarting Pods doesn't make the new logs show up, it seems.
A possible problem to take into account is that these logs can be huge. I have a web application that logs database queries during a synchronization operation and a single synchronization commonly logs about 30 MB of logs. Podman probably handles most of the actual logging, but I thought it might be important whilst designing the UX/UI for it to avoid slow scrolling performance or long lines or something.
The text was updated successfully, but these errors were encountered:
Thanks for your feedback. Hmm, I designed it to follow the logs. It's weird that it's not working for you.
Hmm, it seems this container is a special snowflake somehow. I have another image just using the Adminer image from Dockerhub that works fine, but this application is a NestJS application based on node:17-alpine. All I see is this:
> project-name@0.0.1 start:dev
> nest start --watch "the-application"
Info Webpack is building your sources...
Normally if you make a change then, it adds more content, which does work with podman-compose logs -f, but it doesn't show up in Pods for some reason.
The recently added "Logs" tab is great! Would it be possible to make it automatically refresh or "follow" the logs? Alternatively, a refresh button could also work. I can use
podman-compose logs -f <container>
to follow the logs, but Pods doesn't update alongside with new output; even restarting Pods doesn't make the new logs show up, it seems.A possible problem to take into account is that these logs can be huge. I have a web application that logs database queries during a synchronization operation and a single synchronization commonly logs about 30 MB of logs. Podman probably handles most of the actual logging, but I thought it might be important whilst designing the UX/UI for it to avoid slow scrolling performance or long lines or something.
The text was updated successfully, but these errors were encountered: