21 days ago
Three consecutive CLI deployments fail during “Build image” after approximately 2 seconds. No Docker build steps or application errors are logged.
The only build output is:
scheduling build on Metal builder "builder-nwedvx"
scheduling build on Metal builder "builder-nwedvx"
Railway’s deployment diagnosis classifies this as an Infrastructure Error and confirms that no build logs were captured beyond builder scheduling.
Project ID: 0fdfc7e3-f5f4-49eb-9ccc-b61c5debc331
Service ID: 79f91e6b-19ad-4cca-b69c-f4d5b7a931be
Latest deployment ID: c5cb05b3-3e0d-4c5c-8a2d-ea72e29cb850
The Dockerfile path and deployment configuration are recognized correctly by Railway. Please investigate and reassign or repair the affected Metal builder.
3 Replies
Status changed to Awaiting Railway Response Railway • 21 days ago
20 days ago
A new controlled deployment attempt failed identically on the same Metal builder.
New deployment ID:
cf07bfed-bfa3-46dc-81e3-388d685aa071
Builder:
builder-nwedvx
The build again stopped immediately after the scheduling messages, before any Docker build step started. Please investigate or reassign the affected builder.
20 days ago
Hey! If you take a look at your build logs I can see the following:
dockerfile invalid: docker VOLUME at Line 20 is not supported, use Railway Volumes
Please remove theVOLUME directive from your docker file and use railway volumes to persist volumes instead
Status changed to Awaiting User Response Railway • 20 days ago
20 days ago
Resolved. Removing the Docker VOLUME directive exposed two additional build issues, which have now also been fixed. Deployment 4acd51de-2c65-46bc-9245-6d2d05a9d4bd is online and healthy. Thank you.
Status changed to Awaiting Railway Response Railway • 20 days ago
Status changed to Solved Railway • 20 days ago