Build logs and log files from the app
Hi there, thank you for providing an amazing service!
However, it would be immensely helpful to see
- more explicit logs than you currently provide, especially during the build phase. I recently had a rather cryptic error during the build phase of my Django project ("We failed to create a container for this image."), well not very explicit. It took a test on my own docker to container to get the message that revealed the idiotic mistake (gunicorn missing from requirements...) ("docker: [...] unable to start container process: exec: "gunicorn": executable file not found in $PATH: ...etc."). Anyway, seeing the error straight away would have been a real timesaver. Is there any place where you can find more info if you get an unspecific error message like I did ?
- to be able to see .log files once the app is deployed. Does a shell access option exist on the hobby plan, and if not, on other plans ?
Many thanks in advance, Best regards
Solution:Jump to solution
more explicit logs than you currently providefailed docker builds are very cryptic, not much railway can do about that, if you have any build errors in the future use this https://bookmarklets.up.railway.app/log-downloader/ then come here for support!
to be able to see .log files once the app is deployed. Does a shell access option exist on the hobby plan, and if not, on other plans ?shell access isnt provided on any plan, but it shoudnt be needed for this scenario, you can view the logs in the dashboard https://docs.railway.app/deploy/logging...
4 Replies
Project ID:
N/An/a
Solution
more explicit logs than you currently providefailed docker builds are very cryptic, not much railway can do about that, if you have any build errors in the future use this https://bookmarklets.up.railway.app/log-downloader/ then come here for support!
to be able to see .log files once the app is deployed. Does a shell access option exist on the hobby plan, and if not, on other plans ?shell access isnt provided on any plan, but it shoudnt be needed for this scenario, you can view the logs in the dashboard https://docs.railway.app/deploy/logging make sure you are logging to stdout and or stderr instead of a log file, and double make sure you arent buffering logs
Not related to builds, but we are currently discussing other logs we can add from various systems (eg. network) to provide even more context, so this feedback is super useful