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
Cannot see app logs when a build is running #5234
Comments
I think the system is acting as configured. You have zero downtime deploys disabled, so during a deploy, the existing container will be stopped/removed, and the new container will be placed. Because of that, the Aside, you may wish to update the |
Looking for an app standpoint, I think all the logs should be available, no matter if only for the current deploy or not. The current behavior makes it impossible to investigate past problems after a deploy. =/ (we'd need to store all the logs in another place) About letsencrypt: thanks, I'll update. |
I agree that it would be great to persist logs across deployments automatically. We're unfortunately not going to implement that, as doing so is quite a bit more work than you'd expect. Here are a few things I can think of off the top of my head:
I hope that gives some context as to why nothing is going to be changed there. I'll file an MR to update docs and make it more clear that if you want to persist logs across deploys, you should ship them externally. |
While it is unfortunate that we don't store logs locally, doing so is actually a fairly difficult ask. Rather than pretending the problem doesn't exist, we'll clarify how logs are currently fetched, as well as point users to integrations/tools that may make their lives easier. Refs #5234
Description of problem
I was trying to check the app logs while running a
git push
to this app's repo on Dokku in another shell and got "Error: No such container".# dokku --version dokku version 0.27.6
# dokku logs -n 5000 myapp Error: No such container: e25fd501fd4a129f9eaf6b7d3e5c9871844f05a8a63b78f5d1512f9628b41755
Steps to reproduce
git push
to an app in one terminaldokku logs app
in another onedokku report $APP_NAME
Additional information
No response
Output of failing commands after running: dokku trace:off
No response
Output of failing commands after running: dokku trace:on
No response
The text was updated successfully, but these errors were encountered: