4 months ago
Hi,
One of my recent deployments failed during the "Build › Build image" step (after 9 seconds). The Deploy Logs say "Failed to build an image. Please check the build logs for more details."
However, when I navigate to the Build Logs tab, there are no meaningful log entries — only two lines showing the build being scheduled on Metal builder "builder-cbuxkt" at 06:49:50 and 06:49:58. There is no error output, no build output, and no indication of what went wrong.
This makes it impossible to debug the issue on my end. Could you please look into:
1. Why the build logs are empty despite the build failing.
2. Whether there was an issue with the Metal builder (builder-cbuxkt) that prevented the build from running or logging properly.
3. Any internal error details that could help me resolve this.
I've attached screenshots of both the Deploy Logs (showing the failure) and the Build Logs (showing the empty output) for reference.
Thanks for your help.
Attachments
12 Replies
4 months ago
Howdy!
Are you still running into this consistently? We have a project going on that'll be fixing a few parts of the flow for metal builders.
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
I'm having this same issue. I also tried turning off Metal builders and got the same result. Any idea what's going on here?
Status changed to Awaiting Railway Response Railway • 4 months ago
msgerbush
I'm having this same issue. I also tried turning off Metal builders and got the same result. Any idea what's going on here?
4 months ago
Could I ask you to open your own thread? Since you mentioned turning off the metal builders didn't help, it is likely unrelated to OP's issue.
Status changed to Awaiting User Response Railway • 4 months ago
brody
Could I ask you to open your own thread? Since you mentioned turning off the metal builders didn't help, it is likely unrelated to OP's issue.
4 months ago
FYI, I tried toggling Metal builders again and that resolved the issue, so I do think it was the same problem. Happy to turn it back on and help troubleshoot, if needed.
Status changed to Awaiting Railway Response Railway • 4 months ago
Status changed to Awaiting User Response sam-a • 4 months ago
noahd
Howdy! Are you still running into this consistently? We have a project going on that'll be fixing a few parts of the flow for metal builders.
4 months ago
Oddly don't seem to get email notifications here (I'll investigate that on my end). Yes, this problem is still occurring. None of my recent builds have any logs.
Status changed to Awaiting Railway Response Railway • 4 months ago
kennyjwilli
Oddly don't seem to get email notifications here (I'll investigate that on my end). Yes, this problem is still occurring. None of my recent builds have any logs.
4 months ago
In my most recent successful build + deploy, this is the entirety of the logs in the Build Logs tab:
scheduling build on Metal builder "builder-cbuxkt"
scheduling build on Metal builder "builder-cbuxkt"
==================== Starting Healthcheck ====================
Path: /api/health
Retry window: 5m0s
[1/1] Healthcheck succeeded!
kennyjwilli
In my most recent successful build + deploy, this is the entirety of the logs in the Build Logs tab: scheduling build on Metal builder "builder-cbuxkt" scheduling build on Metal builder "builder-cbuxkt" \==================== Starting Healthcheck ==================== Path: /api/health Retry window: 5m0s \[1/1\] Healthcheck succeeded!
4 months ago
That, to me, looks like this problem has been solved.
Status changed to Awaiting User Response Railway • 4 months ago
brody
That, to me, looks like this problem has been solved.
4 months ago
Erm, how come? I suppose my expectation is that I would see logs of the docker image build steps. On failure, I’d expect some sort of error message.
Status changed to Awaiting Railway Response Railway • 4 months ago
Status changed to Awaiting User Response Railway • 4 months ago
4 months ago
Hello!
We've escalated your issue to our engineering team.
We aim to provide an update within 1 business day.
Please reply to this thread if you have any questions!
4 months ago
I think for full 100% cached builds we're not showing the logs. We can look into it in the future
jake
I think for full 100% cached builds we're not showing the logs. We can look into it in the future
4 months ago
Hi Jake. Thanks for the quick reply! Showing logs for cached builds could make sense. Though, perhaps a short-term fix would be to indicate the build is cached and logs are elided for cached builds.
I'm also not certain that is what is going on here. I just pushed a change to the Dockerfile where I changed the docker base. This is the entirety of the logs I observe in the "Build Logs" tab.
My expectation is that the build logs would show docker build logs, akin to what you'd typically see on CI.
Attachments