2 months ago
the single log line ("scheduling build on Metal builder") followed by immediate failure — this pattern points to builder infrastructure problems, not code issues.
efe5ab05-e41e-48b7-8ff2-23acacc2dff0 (original failure)
8cc1b03f-2051-4563-9284-f2ff89a0f7bb (redeploy attempt)
could you please fix.
1 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
Your build is failing on the VOLUME ["/data"] line in your Dockerfile. Railway's builder rejects the Docker VOLUME instruction, so the build stops before it starts, and a bug on our side meant that error never made it into your logs. Remove that line and add a Railway Volume mounted at /data instead, from your service's Settings.
Status changed to Awaiting User Response Railway • 2 months ago
2 months 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 • 2 months ago