Project: S2F-Staffing Service: web Region: sfo Builder: builder-ufizve (Metal) Builder system: Railpack (buildEnvironment V3) Every deploy of commit e4f002c fails in Build → Build image, before any app build steps. Dashboard build log shows: [railpack] loading secrets unexpected status from HEAD request to https://registry-1.docker.io/v2/library/... Failed deployment IDs (all same commit, all on builder-ufizve): - 09e967a5-9259-460f-be36-1d705091f68b - 4d3dfe32-94a5-46d1-bbd3-9a1bca9f5657 - fac82856-d9f0-4313-8b7e-60139ea7eee7 - d8d6b29d-dbec-480f-a93c-7d160023b4a6 Last successful deploy was ~20 minutes earlier on the same service: - 11b70a2a-92c6-4880-9e41-16ae742844b8 (commit d9e368e) No Dockerfile / railpack.json / build config changed between the successful and failed deploys — only app code for a forgot-password feature. Production is still Online on the previous successful deployment. I redeployed multiple times; every attempt schedules on builder-ufizve and fails the same way in ~10s. Platform diagnosis classifies these as infra_error. Railway and Docker Hub status pages show green. This matches prior Metal builder Docker Hub egress issues. Can you check builder-ufizve or reassign builds for this service to a healthy builder?

Builds stuck on builder-ufizve — Docker Hub HEAD fails before Railpack runs

adamcshelton-hub

HOBBYOP

an hour ago

Project: S2F-Staffing

Service: web

Region: sfo

Builder: builder-ufizve (Metal)

Builder system: Railpack (buildEnvironment V3)

Every deploy of commit e4f002c fails in Build → Build image, before any app build steps. Dashboard build log shows:

[railpack] loading secrets

unexpected status from HEAD request to https://registry-1.docker.io/v2/library/...

Failed deployment IDs (all same commit, all on builder-ufizve):

09e967a5-9259-460f-be36-1d705091f68b
4d3dfe32-94a5-46d1-bbd3-9a1bca9f5657
fac82856-d9f0-4313-8b7e-60139ea7eee7
d8d6b29d-dbec-480f-a93c-7d160023b4a6

Last successful deploy was ~20 minutes earlier on the same service:

11b70a2a-92c6-4880-9e41-16ae742844b8 (commit d9e368e)

No Dockerfile / railpack.json / build config changed between the successful and failed deploys — only app code for a forgot-password feature. Production is still Online on the previous successful deployment.

I redeployed multiple times; every attempt schedules on builder-ufizve and fails the same way in ~10s. Platform diagnosis classifies these as infra_error. Railway and Docker Hub status pages show green.

This matches prior Metal builder Docker Hub egress issues. Can you check builder-ufizve or reassign builds for this service to a healthy builder?

Solved

2 Replies

Status changed to Awaiting Railway Response Railway • about 1 hour ago

chandrika

EMPLOYEE

37 minutes ago

Hey! We're seeing image pulls from Docker Hub fail with a "429 Too Many Requests" error across builds and deployments right now. This is on our side and not something in your project or Dockerfile, so there's nothing you need to change.

The team is investigating now. Once it's resolved, redeploying the failed deployment should go through. We'll follow up here when it's fixed, but please let us know if your deploy still fails after that.

Status changed to Awaiting User Response Railway • 37 minutes ago

chandrika

EMPLOYEE

19 minutes ago

Quick update: this is caused by an ongoing Docker Hub incident that's making image pulls fail. You can follow their updates here: https://www.dockerstatus.com/incidents/01M4HA1E00AH6NXA276AW0CK2V

Once it's resolved, redeploying should go through. We'll let you know here when pulls are working again.

Status changed to Solved adamcshelton-hub • 10 minutes ago

Welcome!