Build failing consistently — builder cannot reach Docker Hub (i/o timeout)
yudiarnanda
FREEOP

43 minutes ago

Project: dirtyline-manager

Service: dirtyline-manager-production

Builder: builder-rjjayj (Metal builder)

Every build attempt is failing at the same step: "load metadata for

docker.io/library/node:20-alpine" with a network timeout error:

failed to solve: DeadlineExceeded: node:20-alpine: failed to resolve

source metadata for docker.io/library/node:20-alpine: failed to do

request: Head "https://registry-1.docker.io/v2/library/node/manifests/20-alpine":

dial tcp :443: i/o timeout

This has happened across multiple attempts over the last ~20 minutes,

with different resolved IPs each time (100.58.88.94, 23.20.232.38,

184.192.139.247) and different image tags (node:20-alpine, node:20-alpine3.20).

I also tried triggering a fresh build via an empty commit to get a

different builder assignment, but the same builder (builder-rjjayj) and

same error persisted.

Railway status page shows all green, so this looks like an issue specific

to this builder's network path to Docker Hub. Could you check builder

"builder-rjjayj" or reassign my build to a different builder?

Failed deployment IDs: 9ad364b1, 084458b7

Awaiting Railway Response

0 Replies

Status changed to Awaiting Railway Response Railway 41 minutes ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...