21 days ago
Every deployment in my project fails ~2-6 seconds after upload, at the "Build > Build image" step, with the message "Failed to build an image. Please check the build logs for more details." The build logs contain only:
scheduling build on Metal builder "builder-jdquku"
scheduling build on Metal builder "builder-jdquku"
No further output — the build never actually starts. This happens consistently (5+ attempts):
with both Railpack auto-detection AND an explicit Dockerfile (plain node:22-alpine)
for two different services (Node.js API and a Vite static frontend)
via CLI railway up (v5.30.1)
before and after upgrading my workspace from Trial to Hobby
Region: US West. Railway status page shows no incidents.
Project ID: 497c41d1-fc30-461d-b951-f41f56b255e7
Service api: e248c065-bc71-4323-9763-a589c8e329e2
Service web: f034e128-16f5-435e-8f1c-11792aeb3299
Example failed deployments: 2fc4fea7-1df3-41db-8a5f-f6166851cf81, d3d3475b-a2c6-4bab-9b0a-9988b9e16b22, b430b4fa-6032-406e-aaf3-602a20cc5e92
Could you check what is killing these builds on your side?
It looks like the workspace/builds are being rejected before execution.
Thank you!
=)
1 Replies
Status changed to Awaiting Railway Response Railway • 21 days ago
21 days ago
Hey! this was likely because it appears you were using the express preview.
Express uses neither dockerfile or railpack to build and is still experimental in nature. I can see you have had healthy deploys since then so you should be all good to go. Let me know if you're still having trouble anywhere
Status changed to Awaiting User Response Railway • 21 days ago
14 days ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 14 days ago