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
Automatically "follow" logs #139
Comments
Thanks for your feedback. Hmm, I designed it to follow the logs. It's weird that it's not working for you. Line 644 in 6748af3
Oh yeah, good point. We should probably work with |
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
Normally if you make a change then, it adds more content, which does work with |
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: