Open lucasassisrosa opened 4 months ago
[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 /appERROR: 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.
thats my case
Sorry for the delay. For those facing issues is it intermittent or consistent? Can you run the following
@lucasassisrosa:
curl -A github165 -v mcr.microsoft.com/v2/playwright:v1.37.0-focal/manifests/sha256:76de21fcd165e867021bc510c7cdf1811b68b518ba11a2101c3ec7d737eed831
@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.
Same issue here guys, any updates? Running these curl commands result in:
Sorry for late, guys.
I forgot to say that, downgrading the docker, it worked. I am using the version below:
Looks like a docker desktop issue.
Sorry for the delay. For those facing issues is it intermittent or consistent? Can you run the following
@lucasassisrosa:
curl -A github165 -v mcr.microsoft.com/v2/playwright:v1.37.0-focal/manifests/sha256:76de21fcd165e867021bc510c7cdf1811b68b518ba11a2101c3ec7d737eed831
@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.
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. Im using mcr.microsoft.com/dotnet/aspnet:7.0 and mcr.microsoft.com/dotnet/sdk:7.0
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:
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
Any news on this without downgrading Docker?
mcr.microsoft.com
solved by turning off IPv6 on Win11 pro 23H2The 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
I ended up having to downgrade to 4.32.0 (157355). That works fine for us. https://docs.docker.com/desktop/release-notes/
Downgrade solved my problem as well, thank you!
I try to downgrade to 4.32.0 and switch off IPv6 - doesn't help. Windows 10 Pro 22H2
Upgrading Docker Desktop (to 4.36.0) solved my issue
The problem was with my antivirus, after reinstalling the antivirus the docker started working.
Upgraded Docker Desktop and it's solved now
v4.36.0
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?
For me downgrade to v4.32 to solve it :)
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: