6 days ago
Domain: playbookone-api.up.railway.app
Builder: builder-fstdwd
Every deploy attempt on this service has failed for the last ~24 hours, all in the exact same way: the build log ends immediately after scheduling build on Metal builder "builder-fstdwd"...no pip install output, no compiler error, no dependency conflict, nothing. Just a hard stop with "Failed to build an image."
Failed deployment IDs: 1f05076e, fb93b3c5, abd908d6 (and at least one more since).
The commits triggering these deploys vary and aren't related to each other (some don't even touch this service's files), so it doesn't look like a code issue. Railway's Diagnose tool flagged one of these as an Infrastructure Error, unrelated to the triggering commit.
Note: the one deployment that succeeded (build 51cf6c37) predates all of these failures.....nothing has rebuilt successfully since, regardless of what changed.
One more data point: my Settings page shows the service's builder as Nixpacks — flagged "Deprecated" by Railway itself. Wondering if that's related — is Metal deprioritizing/mishandling builds still routed through the deprecated Nixpacks builder? If migrating to Railpack is the actual fix rather than a Metal-specific workaround?
I now have 3 different builder instances (builder-fstdwd, builder-wdwizw, builder-niacvm) failing the same way across two different services in the same project
1 Replies
6 days ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • 6 days ago
6 days ago
Disable Metal Build Environment on the affected services and redeploy.
If that works, migrate those services to Railpack and re-enable Metal later if you want.
If both still fail, open a thread on station.railway.com with the domain, the builder names, and the failed deployment IDs (1f05076e, fb93b3c5, abd908d6, etc.). Mention that Diagnose already flagged an Infrastructure Error and that multiple Metal builders are affected across services.
Turn off Metal Build Environment (most reliable short-term fix)
Service Settings → look for “Use Metal Build Environment” (or similar) → disable it → save → redeploy.
Many users with identical empty-log failures on Metal builders got successful builds immediately after turning this off.
Migrate the service from Nixpacks → Railpack (recommended longer-term fix) Go to the service Settings.
Change the builder from Nixpacks (Deprecated) to Railpack.
Or set in railway.json / railway.toml:
{
"build": {
"builder": "RAILPACK"}
}
redeploy it lmk how it goes