503 error when pulling image from mcr.microsoft.com

liam-careerhub commented 1 year ago

Hi, pulling containers fails with a 503 error.

Example command: docker pull mcr.microsoft.com/dotnet/framework/aspnet:4.8-windowsservercore-ltsc2022

output: Error response from daemon: received unexpected HTTP status: 503 Service Unavailable

Tried with a few images, and from a few machines and internet connections. Is there anything that can be done to increase reliability? I see another issue logged in November where it went down, I'm a bit nervous about setting up a production pipeline with these images because of it.

Thanks.

baynewc1 commented 1 year ago

This is also affecting us

jxdn commented 1 year ago

same here, how to check if the services is up or down ?

koraybalci commented 1 year ago

Same here, perhaps this is the page? https://azure.status.microsoft/en-us/status seems like the status link.. (Azure Container Service)

ltankey commented 1 year ago

~~It appears to be back up now.~~

I think it's having a moment -- was temporarily up and is down again.

➜  docker pull mcr.microsoft.com/azure-functions/node:4-node16-appservice
Error response from daemon: received unexpected HTTP status: 503 Service Unavailable
➜  docker pull mcr.microsoft.com/azure-functions/node:4-node16-appservice
Error response from daemon: received unexpected HTTP status: 503 Service Unavailable
➜  docker pull mcr.microsoft.com/azure-functions/node:4-node16-appservice
4-node16-appservice: Pulling from azure-functions/node
025c56f98b67: Downloading [=>                                                 ]    653kB/31.41MB
b7bdfde7680c: Downloading [==============>                                    ]  4.258MB/14.97MB
6942e6b85cae: Downloading [>                                                  ]  3.242MB/194MB
...

AndreHamilton-MSFT commented 5 months ago

This was transient. Please file a new item if you continue to see issues

microsoft / containerregistry

503 error when pulling image from mcr.microsoft.com #131