Skip to content
Repeated builds fail resolving
suf-sk
OP

a month ago

Repeated builds fail resolving node:24.21.0-bookworm-slim. Docker Hub’s manifest HEAD request returns HTTP 429 before any application build steps. Please check registry access/rate limiting on the assigned builder.

Solved

4 Replies

Railway
BOT

a month ago

We're sorry for the trouble. We're aware of an issue causing builds and deploys to fail with "429 Too Many Requests" when pulling images from Docker Hub, and we're actively investigating. You can follow updates at the incident page.


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

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.

suf-sk
OP

a month ago

thanks


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


chandrika
EMPLOYEE

a month ago

The Docker Hub incident is resolved and node:24.21.0-bookworm-slim is pulling normally again. Redeploying should go through now.


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


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...