Skip to content
Repeated Railpack builds fail pulling alpine:latest with Docker Hub 429
aibotshubham
OP

a month ago

Our app service in project exquisite-heart (production) has failed to deploy three times with the same Docker Hub error. The previous successful deployment remains online, but we cannot deploy the latest change.

Build error:

failed to solve: failed to load cache key: unexpected status from HEAD request to https://registry-1.docker.io/v2/library/alpine/manifests/latest: 429 Too Many Requests

The failure is reported at [railpack] loading secrets, before the application compiles. Logs identify Railpack 0.40.1 and Metal builder builder-nmkmhs. Retrying the same commit twice has not helped. The app build and tests pass locally.

Project ID: 0725ee18-6aa7-4089-a4df-9bba39c11e06

Environment: production

Service: app

Commit: 1580a5a0729ccfe8beb0b9dad8cd1238f1bfd171

Failed deployment IDs:

8a95423d-9341-4b73-a033-ec34c8bfa5bf

67b6a282-e2e2-4188-b7cd-75f99b6ab45b

78857495-16cd-4d6f-9ef5-90b76341b312

We see incident O3D8H5MZ is being investigated. Could you confirm that these deployments are affected and advise whether we should simply wait for resolution or use a supported workaround?

Solved

4 Replies

Railway
BOT

a month ago

We're sorry for the trouble. Your three failed deployments of the app service started about 13 minutes after we posted the Builds and deploys failing to pull images from Docker Hub incident. They show the same "429 Too Many Requests" error that incident describes, which happened when your build pulled alpine:latest from Docker Hub.

The incident is still being investigated. Your app code isn't the cause, and redeploying the same commit can keep hitting the same error until this is fixed. Your previous successful deployment is still serving traffic. The simplest option is to wait and redeploy once the incident is resolved.


Status changed to Awaiting User Response Railway • about 1 month ago


chandrika
EMPLOYEE

a month 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.


chandrika
EMPLOYEE

a month ago

Waiting was the right call. The Docker Hub incident is resolved and alpine:latest is pulling again, so redeploying should work now.


aibotshubham
OP

a month ago

Okay thank you team


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


Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...