5 months ago
My Flutter Web service has been stuck on "scheduling build on Metal builder (builder-cbuxkt)" for over 10 minutes without executing a single line of the Dockerfile. The build never starts and eventually fails with "Failed to build an image."
What I've tried:
- Multiple redeployments
- Switched builder back and forth between Nixpacks and Dockerfile
- Updated the Dockerfile to use a lighter base image (debian:bookworm-slim instead of ghcr.io/cirruslabs/flutter:stable)
- Verified Root Directory and Dockerfile path (/Dockerfile) are correct
Build logs only show:
```
scheduling build on Metal builder "builder-cbuxkt"
scheduling build on Metal builder "builder-cbuxkt"
Setup:
- Branch: main
- Builder: Dockerfile at /Dockerfile
- No Root Directory set (Dockerfile is at repo root)
- Plan: Hobby (paid)
This seems to be an infrastructure issue on Railway's side as the configuration is correct and was working before. Please advise.
9 Replies
Status changed to Awaiting User Response Railway • 5 months ago
5 months ago
same problem here.
Status changed to Awaiting Railway Response Railway • 5 months ago
5 months ago
Same here too
brody
Hello, We have escalated this so the platform team can take a look at it.
5 months ago
Same for me too
5 months ago
Same problem for me.
5 months ago
Same problem. I have a fastapi service, and it usually builds and deploys in under a minute. Going on 8 minutes when I canceled, and the only thing in the log is:
scheduling build on Metal builder "builder-xayinw"
EDIT: I got it to build and deploy by turning off "Use Metal Build Environment" in settings.
ohcedar
Same problem. I have a fastapi service, and it usually builds and deploys in under a minute. Going on 8 minutes when I canceled, and the only thing in the log is: scheduling build on Metal builder "builder-xayinw" EDIT: I got it to build and deploy by turning off "Use Metal Build Environment" in settings.
5 months ago
that saved me. thanks.
5 months ago
SAME HERE FOR ME
uxmohamed
SAME HERE FOR ME
5 months ago
See my post above. I found a workaround.
