a month ago
Getting aBuild Failed: [bc.Build](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 month ago
Can you check if the metal builder is enabled?
a month ago
Yeah
a month ago
For a quick fix that is
a month ago
I don't know what they changed with metal builder and Dockerfile paths
a month ago
I expect them to fix it soon enough
a month ago
They are seemingly slowly rolling it out
a month ago
Brody, what changed with Dockerfile paths…?
a month ago
also why are you rolling it out and still have this tag

a month ago
Rolling out to Free/Trail/Hobby
a month ago
Those plans are not to be used for production workloads.
a month ago
fair enough
a month ago
use them as beta testers :P
a month ago
Kinda
a month ago
you are the test subject
a month ago
how do you feel
a month ago
Will report this either way.
a month ago
Dockerfile detection fault on builder v3
a month ago
Can you provide a link to that failed deployment so we can look into it?
a month ago
Here is fine, a link is not sensitive information
a month ago
Regular people like me can't actually view it anyways
a month 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.