Error response from daemon: Get "https://mcr.microsoft.com/v2/": EOF

[shibayan]

Pulling images from MCR is not successful at all. The TLS connection fails at a very high rate, making Dev Container and others unusable.

*   Trying 204.79.197.219:443...
* Connected to mcr.microsoft.com (204.79.197.219) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
*  CAfile: /etc/ssl/certs/ca-certificates.crt
*  CApath: /etc/ssl/certs
* TLSv1.0 (OUT), TLS header, Certificate Status (22):
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* OpenSSL SSL_connect: Connection reset by peer in connection to mcr.microsoft.com:443
* Closing connection 0
* TLSv1.0 (OUT), TLS header, Unknown (21):
* TLSv1.3 (OUT), TLS alert, decode error (562):
curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to mcr.microsoft.com:443

*   Trying 204.79.197.219:443...
* Connected to mcr.microsoft.com (204.79.197.219) port 443 (#0)
* schannel: disabled automatic use of client certificate
* ALPN: offers http/1.1
* schannel: failed to receive handshake, SSL/TLS connection failed
* Closing connection 0
curl: (35) schannel: failed to receive handshake, SSL/TLS connection failed

[sjasct]

Been seeing the same this morning for the .NET 6 SDK image on Azure Pipelines (Hosted Agent). Some pulls are working fine, but other runs seem to error out.

Step 3/33 : FROM mcr.microsoft.com/dotnet/sdk:6.0 AS build
Get "[https://mcr.microsoft.com/v2/"](https://mcr.microsoft.com/v2/%22): net/http: TLS handshake timeout
##[error]Get "[https://mcr.microsoft.com/v2/"](https://mcr.microsoft.com/v2/%22): net/http: TLS handshake timeout
##[error]The process '/usr/bin/docker' failed with exit code 1

[AndreHamilton-MSFT]

This should be resolved. @sjasct @shibayan please let me know if you are still seeing this.

[shibayan]

This problem no longer occurs in my environment. Thank you very much.