-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mcr.microsoft.com hanging: pulling images failed #165
Comments
#1 [internal] load build definition from Dockerfile #2 [internal] load metadata for mcr.microsoft.com/dotnet/sdk:8.0 #3 [internal] load metadata for mcr.microsoft.com/dotnet/aspnet:8.0
|
Sorry for the delay. For those facing issues is it intermittent or consistent? Can you run the following
In the output of the curl command succeeded you should see an x-msedge-reg value. If you can share that value it would be great. This will help us narrow down where this issue is occurring. Also run it a few times so we have a few values to look into. |
Same issue here guys, any updates? Running these curl commands result in:
|
Looks like a docker desktop issue. |
|
It is consistent. I will downgrade my version to 4.32 to confirm that it is a docker desktop issue. Stand by. |
Confirmed. Everything is stable using Docker Desktop version 4.32. Thanks - I will follow this thread for further updates and stay on 4.32 in the mean time. |
I'm having the same problem right now building my images using jenkins and a linux machine. The only solution for me was to download the images before hand and build after that. |
Has anyone resolved this other than by downgrading? The same issue is occurring consistently with podman. Running the curl command as requested seems successful (I get < X-MSEdge-Ref: Ref A: 9F14B8D7F3A74CFAAE7B50947911C634 Ref B: EWR311000107049 Ref C: 2024-09-11T14:39:47Z and a list of checksums, etc.) but when running a build, it's all I/O timeout errors. Very confusing and frustrating. |
I downgraded to 4.32MacOS Silicon too, I was experiencing the following issues. broken build because of a network issue only when OpenVPN was enabled: connecting to an API endpoint from inside a running container was broken, and timeouting during the authentication endpoint. discovery from inside a running container: Authentication issues to pull images |
Any news on this without downgrading Docker? |
Failing to pull docker images from
|
I ended up having to downgrade to 4.32.0 (157355). That works fine for us. |
Downgrade solved my problem as well, thank you! |
I try to downgrade to 4.32.0 and switch off IPv6 - doesn't help. |
Upgrading Docker Desktop (to 4.36.0) solved my issue |
The problem was with my antivirus, after reinstalling the antivirus the docker started working. |
Hi there,
we're having issues since yesterday on pulling images from
mcr.microsoft.com
. It's hanging forever or failing withconnection reset
.Image we're trying to pull now is:
mcr.microsoft.com/playwright:v1.37.0-focal@sha256:76de21fcd165e867021bc510c7cdf1811b68b518ba11a2101c3ec7d737eed831
. We also tried with a different playwright version.Issue log:
The text was updated successfully, but these errors were encountered: