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

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