a year ago
Getting a Build Failed: bc.Build: failed to solve: failed to read dockerfile: open backend/Dockerfile: no such file or directory
Railway instance is connected to my github branch, and no files related to that file was changed, tried redeploying, still the same error
Am on the hobby plan!
Would love to get help asap as i cannot push to production without getting this fixed : (
Thank you!
30 Replies
a year ago
Can you check if the metal builder is enabled?
a year ago
Yeah
a year ago
For a quick fix that is
a year ago
I don't know what they changed with metal builder and Dockerfile paths
a year ago
I expect them to fix it soon enough
a year ago
They are seemingly slowly rolling it out
a year ago
Brody, what changed with Dockerfile paths...?
a year ago
also why are you rolling it out and still have this tag
a year ago
Rolling out to Free/Trail/Hobby
a year ago
Those plans are not to be used for production workloads.
a year ago
fair enough
a year ago
use them as beta testers :P
a year ago
Kinda
a year ago
you are the test subject
a year ago
how do you feel
a year ago
Will report this either way.
a year ago
Dockerfile detection fault on builder v3
a year ago
Can you provide a link to that failed deployment so we can look into it?
a year ago
Here is fine, a link is not sensitive information
a year ago
Regular people like me can't actually view it anyways
a year ago
It took Claude.ai 25 minutes to convince me it was a Railway issue, not a Claude Code fail. I won't repeat what I said to Claude. But they did not deserve the displeasure I threw at them for f'ing up my backend.