mcr.microsoft.com hanging: pulling images failed · Issue #165 · microsoft/containerregistry · GitHub
Skip to content

mcr.microsoft.com hanging: pulling images failed #165

Open
Open
mcr.microsoft.com hanging: pulling images failed#165
Assignees
AndreHamilton-MSFT

Description

@lucasassisrosa
Lucas Rosa (lucasassisrosa)
opened on Jul 23, 2024

Hi there,

we're having issues since yesterday on pulling images from mcr.microsoft.com. It's hanging forever or failing with connection 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:

20:23:31  #8 sha256:d4ba1144e798cf86d9cad1dc30c84fdab2122da75494e92b92b298f10276b224 83.89MB / 568.48MB 235.7s
20:23:57  #8 sha256:d4ba1144e798cf86d9cad1dc30c84fdab2122da75494e92b92b298f10276b224 0B / 568.48MB 261.0s
20:24:02  #8 sha256:d4ba1144e798cf86d9cad1dc30c84fdab2122da75494e92b92b298f10276b224 14.68MB / 568.48MB 266.0s
20:24:07  #8 sha256:d4ba1144e798cf86d9cad1dc30c84fdab2122da75494e92b92b298f10276b224 14.68MB / 568.48MB 271.2s
20:24:12  #8 sha256:d4ba1144e798cf86d9cad1dc30c84fdab2122da75494e92b92b298f10276b224 14.68MB / 568.48MB 276.2s
20:24:17  #8 sha256:d4ba1144e798cf86d9cad1dc30c84fdab2122da75494e92b92b298f10276b224 14.68MB / 568.48MB 281.4s
20:24:22  #8 sha256:d4ba1144e798cf86d9cad1dc30c84fdab2122da75494e92b92b298f10276b224 14.68MB / 568.48MB 286.6s
20:24:25  #8 ERROR: failed to copy: read tcp 10.97.134.229:39880->150.171.69.10:443: read: connection reset by peer
20:24:25  ------
20:24:25   > [build 1/6] FROM mcr.microsoft.com/playwright:v1.37.0-focal@sha256:76de21fcd165e867021bc510c7cdf1811b68b518ba11a2101c3ec7d737eed831:
20:24:25  ------
20:24:25  failed to copy: read tcp 10.97.134.229:39880->150.171.69.10:443: read: connection reset by peer

Activity

  1. bsallesp commented on Jul 27, 2024

    @bsallesp
    Bruno S Pereira (bsallesp)
    on Jul 27, 2024

    #1 [internal] load build definition from Dockerfile
    #1 transferring dockerfile: 1.08kB 0.0s done
    #1 DONE 0.0s

    #2 [internal] load metadata for mcr.microsoft.com/dotnet/sdk:8.0
    #2 ERROR: failed to do request: Head "https://mcr.microsoft.com/v2/dotnet/sdk/manifests/8.0": EOF

    #3 [internal] load metadata for mcr.microsoft.com/dotnet/aspnet:8.0
    #3 ERROR: failed to do request: Head "https://mcr.microsoft.com/v2/dotnet/aspnet/manifests/8.0": EOF

    [internal] load metadata for mcr.microsoft.com/dotnet/sdk:8.0:

    [internal] load metadata for mcr.microsoft.com/dotnet/aspnet:8.0:

    Dockerfile:3

    1 | #See https://aka.ms/customizecontainer to learn how to customize your debug container and how Visual Studio uses this Dockerfile to build your images for faster debugging.
    2 |
    3 | >>> FROM mcr.microsoft.com/dotnet/aspnet:8.0 AS base
    4 | USER root
    5 | WORKDIR /app

    ERROR: failed to solve: mcr.microsoft.com/dotnet/aspnet:8.0: failed to resolve source metadata for mcr.microsoft.com/dotnet/aspnet:8.0: failed to do request: Head "https://mcr.microsoft.com/v2/dotnet/aspnet/manifests/8.0": EOF

    View build details: docker-desktop://dashboard/build/default/default/pgs4yqanfnc4gkq08vsrbq6a2
    C:\Users\bsall\source\repos\Quiztle\Quiztle.API\Dockerfile(0,0): Error CTC1014: Docker command failed with exit code 1.
    #0 building with "default" instance using docker driver

    #1 [internal] load build definition from Dockerfile
    #1 transferring dockerfile: 1.08kB 0.0s done
    #1 DONE 0.0s

    #2 [internal] load metadata for mcr.microsoft.com/dotnet/sdk:8.0
    #2 ERROR: failed to do request: Head "https://mcr.microsoft.com/v2/dotnet/sdk/manifests/8.0": EOF

    #3 [internal] load metadata for mcr.microsoft.com/dotnet/aspnet:8.0
    #3 ERROR: failed to do request: Head "https://mcr.microsoft.com/v2/dotnet/aspnet/manifests/8.0": EOF

    thats my case

  2. AndreHamilton-MSFT commented on Jul 29, 2024

    @AndreHamilton-MSFT
    AndreHamilton-MSFT
    on Jul 29, 2024
    Member

    Sorry for the delay. For those facing issues is it intermittent or consistent? Can you run the following

    Lucas Rosa (@lucasassisrosa):

    curl -A github165 -v mcr.microsoft.com/v2/playwright:v1.37.0-focal/manifests/sha256:76de21fcd165e867021bc510c7cdf1811b68b518ba11a2101c3ec7d737eed831

    Bruno S Pereira (@bsallesp)

    curl -A github165 -v https://mcr.microsoft.com/v2/dotnet/sdk/manifests/8.0

    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.

    image

  3. AndreHamilton-MSFT
    self-assigned this
    on Jul 29, 2024

  4. adanbrownpaca commented on Aug 1, 2024

    @adanbrownpaca
    Adan Brown (adanbrownpaca)
    on Aug 1, 2024

    Same issue here guys, any updates? Running these curl commands result in:

    • Host mcr.microsoft.com:443 was resolved.
    • IPv6: 2603:1061:f:101::10, 2603:1061:f:100::10
    • IPv4: 150.171.70.10, 150.171.69.10
    • Trying [2603:1061:f:101::10]:443...
    • Connected to mcr.microsoft.com (2603:1061:f:101::10) port 443
    • schannel: disabled automatic use of client certificate
    • ALPN: curl offers http/1.1
    • Send failure: Connection was reset
    • schannel: failed to send initial handshake data: sent -1 of 292 bytes
    • Closing connection
    • schannel: shutting down SSL/TLS connection with mcr.microsoft.com port 443
    • Send failure: Connection was reset
    • schannel: failed to send close msg: Failed sending data to the peer (bytes written: -1)
      curl: (35) Send failure: Connection was reset

  5. bsallesp commented on Aug 1, 2024

    @bsallesp
    Bruno S Pereira (bsallesp)
    on Aug 1, 2024

    Sorry for late, guys.

    I forgot to say that, downgrading the docker, it worked.
    I am using the version below:

    image

  6. bsallesp commented on Aug 1, 2024

    @bsallesp
    Bruno S Pereira (bsallesp)
    on Aug 1, 2024

    Looks like a docker desktop issue.

  7. bsallesp commented on Aug 1, 2024

    @bsallesp
    Bruno S Pereira (bsallesp)
    on Aug 1, 2024

    Sorry for the delay. For those facing issues is it intermittent or consistent? Can you run the following

    Lucas Rosa (@lucasassisrosa):

    curl -A github165 -v mcr.microsoft.com/v2/playwright:v1.37.0-focal/manifests/sha256:76de21fcd165e867021bc510c7cdf1811b68b518ba11a2101c3ec7d737eed831

    Bruno S Pereira (@bsallesp)

    curl -A github165 -v https://mcr.microsoft.com/v2/dotnet/sdk/manifests/8.0

    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.

    image

    image

  8. adanbrownpaca commented on Aug 10, 2024

    @adanbrownpaca
    Adan Brown (adanbrownpaca)
    on Aug 10, 2024

    It is consistent. I will downgrade my version to 4.32 to confirm that it is a docker desktop issue. Stand by.

  9. adanbrownpaca commented on Aug 10, 2024

    @adanbrownpaca
    Adan Brown (adanbrownpaca)
    on Aug 10, 2024

    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.

  10. Matheus-SS commented on Aug 26, 2024

    @Matheus-SS
    Matheus Sá dos Santos (Matheus-SS)
    on Aug 26, 2024

    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.
    Im using mcr.microsoft.com/dotnet/aspnet:7.0 and mcr.microsoft.com/dotnet/sdk:7.0

  11. K-Benton-CAVC commented on Sep 11, 2024

    @K-Benton-CAVC
    K-Benton-CAVC
    on Sep 11, 2024

    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.

  12. valentin-pouget-forge commented on Sep 20, 2024

    @valentin-pouget-forge
    valentin-pouget-forge
    on Sep 20, 2024

    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:
    failed to solve: node:20.16.0-alpine: failed to resolve source metadata for docker.io/library/node:20.16.0-alpine: failed to do request: Head "https://registry-1.docker.io/v2/library/node/manifests/20.16.0-alpine": dialing registry-1.docker.io:443 container via direct connection because app settings has no HTTPS proxy: connecting to registry-1.docker.io:443: dial tcp: lookup registry-1.docker.io: no such host

    connecting to an API endpoint from inside a running container was broken, and timeouting during the authentication endpoint. discovery from inside a running container:
    Error in callback: RPError: outgoing request timed out after 3500ms

    Authentication issues to pull images
    failed to solve: node:20.16-alpine: failed to resolve source metadata for [docker.io/library/node:20.16-alpine:](http://docker.io/library/node:20.16-alpine:) failed to authorize: failed to fetch anonymous token: Get "https://auth.docker.io/token?scope=repository%3Alibrary%2Fnode%3Apull&service=registry.docker.io": dial tcp: lookup [auth.docker.io](http://auth.docker.io/) on 127.0.0.11:53: server misbehaving

  13. ggrafhalfbrick commented on Sep 24, 2024

    @ggrafhalfbrick
    ggrafhalfbrick
    on Sep 24, 2024

    Any news on this without downgrading Docker?

  14. peereflits commented on Oct 23, 2024

    @peereflits
    Marcel Peereboom (peereflits)
    on Oct 23, 2024

    Failing to pull docker images from mcr.microsoft.com solved by turning off IPv6 on Win11 pro 23H2

    The error I got, was:

    failed to resolve source metadata for mcr.microsoft.com/dotnet/sdk:8.0: failed to do request: Head "https://mcr.microsoft.com/v2/dotnet/sdk/manifests/8.0": EOF

    After some investigation and testing I was able to solve this issue by disabling IPv6.

    See: https://github.com/peereflits/Articles/blob/main/Other/2024-10-23-failing-to-pull-docker-images.md

  15. ggrafhalfbrick commented on Oct 23, 2024

    @ggrafhalfbrick
    ggrafhalfbrick
    on Oct 23, 2024

    I ended up having to downgrade to 4.32.0 (157355). That works fine for us.
    https://docs.docker.com/desktop/release-notes/

  16. cseuzaron commented on Nov 14, 2024

    @cseuzaron
    cseuzaron
    on Nov 14, 2024

    Downgrade solved my problem as well, thank you!

  17. jabacrack commented on Nov 19, 2024

    @jabacrack
    jabacrack
    on Nov 19, 2024

    I try to downgrade to 4.32.0 and switch off IPv6 - doesn't help.
    Windows 10 Pro 22H2

  18. cesar-albusac commented on Nov 20, 2024

    @cesar-albusac
    César Albusac (cesar-albusac)
    on Nov 20, 2024

    Upgrading Docker Desktop (to 4.36.0) solved my issue

  19. jabacrack commented on Nov 20, 2024

    @jabacrack
    jabacrack
    on Nov 20, 2024

    The problem was with my antivirus, after reinstalling the antivirus the docker started working.

  20. lucasassisrosa commented on Nov 25, 2024

    @lucasassisrosa
    Lucas Rosa (lucasassisrosa)
    on Nov 25, 2024
    Author

    Upgraded Docker Desktop and it's solved now

    v4.36.0

  21. adanbrownpaca commented on Nov 25, 2024

    @adanbrownpaca
    Adan Brown (adanbrownpaca)
    on Nov 25, 2024

    Upgraded Docker Desktop and it's solved now

    v4.36.0

    Lucas, are you confirming that v4.36 now works? Many of us had to downgrade to v4.32 to solve it. Is it now fully resolved?

  22. cesar-albusac commented on Nov 25, 2024

    @cesar-albusac
    César Albusac (cesar-albusac)
    on Nov 25, 2024

    For me downgrade to v4.32 to solve it :)

  23. TimothyHarrelson commented on Dec 3, 2024

    @TimothyHarrelson
    Timothy Harrelson (TimothyHarrelson)
    on Dec 3, 2024

    I have this problem on v4.34 to v4.36, only downgrading to v4.32 has solved the issue for me.

    I only see this issue on my work computer and not my home computer. My work computer uses a proxy (though it still fails to functions with the proxy disabled), and is on Windows 10, while my home computer is on WIndows 11.

    Disabling IPv6 on my network adapter did fix the issue as well.

  24. StormeNet commented on Aug 29, 2025

    @StormeNet
    StormeNet (StormeNet)
    on Aug 29, 2025

    Had this issue with v4.45, and solved it thx to Timothy Harrelson (@TimothyHarrelson) by disabling IPv6 on my network adapter.

  25. brainwipe commented on Mar 20, 2026

    @brainwipe
    Rob Lang (brainwipe)
    on Mar 20, 2026
    > docker pull mcr.microsoft.com/dotnet/aspnet:10.0
Error response from daemon: failed to resolve reference "mcr.microsoft.com/dotnet/aspnet:10.0": failed to do request: Head "https://mcr.microsoft.com/v2/dotnet/aspnet/manifests/10.0": EOF

    Still not working on:

    • Fresh Win 11 Pro, 10.0.26200 Build 26200
    • Docker Desktop Version 4.65.0 (221669) on top of up-to-date WSL2
    • Firewall/Antivirus paused, no affect

    I'm not able to downgrade as ISO27001 and NCSC Cyber Essentials Plus requires we run the latest patched versions of software.

    Disabling ipv6 on the network adapter does work around this issue but it feels like Microsoft Container Registry should investigate a fix.

  26. welyb-alegal commented on Mar 30, 2026

    @welyb-alegal
    Antoine Le Gal (welyb-alegal)
    on Mar 30, 2026

    Same problem here, everything up-to-date (Docker Desktop 4.66.1, Win 11 Pro 26200.8039) and no other problem but with Microsoft Container Registry. Unless IPv6 is disabled the time needed to pull needed images, we cannot pull images from mcr.microsoft.com which is a blocker when heavily working with devcontainers.

  27. jwood-billee commented on May 13, 2026

    @jwood-billee
    Josh Wood (jwood-billee)
    on May 13, 2026

    Still a problem in 2026. Disabling IPv6 temporarily allow me to download the image.

    * Host mcr.microsoft.com:443 was resolved.
* IPv6: 2603:1061:f:100::10, 2603:1061:f:101::10
* IPv4: 150.171.69.10, 150.171.70.10
*   Trying [2603:1061:f:100::10]:443...
* connect to 2603:1061:f:100::10 port 443 from :: port 62686 failed: Network unreachable
...
 X-MSEdge-Ref: Ref A: 79484B8EDF58488FADA4D48C74443F93 Ref B: ATL331000102023 Ref C: 2026-05-13T15:05:06Z
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions