Docker build fails because builder can't pull public MCR base image (401 Unauthorized)
jonkaye
HOBBYOP

2 months ago

Hi! my Dockerfile builds are failing at the base-image pull step, before any

of my code is copied in. The builder gets a 401 pulling Microsoft's public

.NET 10 images from mcr.microsoft.com.

Exact error:

failed to solve: mcr.microsoft.com/dotnet/sdk:10.0: failed to resolve source

metadata for mcr.microsoft.com/dotnet/sdk:10.0: unexpected status from HEAD

request to https://mcr.microsoft.com/v2/dotnet/sdk/manifests/10.0: 401 Unauthorized

(An earlier attempt failed the same way on the token endpoint:

"failed to fetch anonymous token ... GET https://mcrprod.azurecr.io/oauth2/token

?scope=repository:dotnet/aspnet:pull&service=mcrprod.azurecr.io: 401 Unauthorized")

Details:

  • Builder: Metal builder "builder-emkgde"

  • Base images (Dockerfile): mcr.microsoft.com/dotnet/sdk:10.0 and

    mcr.microsoft.com/dotnet/aspnet:10.0

  • Fails on "load metadata for ...:10.0" — i.e. pulling the base image, before COPY.

Why I believe this is on the build infrastructure's path to MCR, not my project:

  • The "10.0" tag is valid and current (it's the GA tag, resolving to 10.0.9) —

    it pulls fine from other networks.

  • These are public, anonymous-pull images; no auth is expected.

  • There's no MCR outage reported on github.com/dotnet/dotnet-docker/issues, so

    this isn't a Microsoft-wide incident.

  • This Dockerfile built successfully on Railway previously; nothing in my image

    definition changed.

What I've tried:

  • Redeployed several times over 30 minutes, but I get the same 401 each time.

Is this builder is being rate-limited or blocked when

pulling anonymously from mcr.microsoft.com / mcrprod.azurecr.io, or whether a

registry pull-through cache / different builder can be used? I just don't know what further to do. Thanks!

Solved$10 Bounty

1 Replies

Railway
BOT

2 months ago

This thread has been opened as a bounty so the community can help solve it.

Status changed to Open Railway 2 months ago


Status changed to Solved jonkaye 2 months ago


jonkaye
HOBBYOP

2 months ago

Seems like 30 mins was the charm. Retrieving and building now, go figure.


Status changed to Awaiting Railway Response Railway 2 months ago


Status changed to Solved Railway 2 months ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...