Builds failing due to Docker registry i/o timeout
evhaus
PROOP

10 months ago

I'm seeing builds failing currently with this error:

[internal] load metadata for docker.io/library/node:22-alpine
failed to do request: Head "https://registry-1.docker.io/v2/library/node/manifests/22-alpine": dial tcp: lookup registry-1.docker.io on 169.254.169.254:53: read udp 172.17.0.5:42461->169.254.169.254:53: i/o timeout

Is this a temporary outage with the Docker registry or a problem at Railway?

Solved

2 Replies

chandrika
EMPLOYEE

10 months ago

Hi there,

I don't believe there weren't any outages at Railway at the time. You can review Docker registry status page here (doesn't look like they had anything then either)

Looking at your linked service they seem to be up and running — are you still running into this issue?

Status changed to Awaiting User Response Railway • 10 months ago

evhaus
PROOP

10 months ago

Must have been a blip in the Docker registry. All good now.

Status changed to Awaiting Railway Response Railway • 10 months ago

Status changed to Solved evhaus • 10 months ago

Loading...