core icon indicating copy to clipboard operation
core copied to clipboard

docker-compose build fails to pull images from mcr.microsoft.com

Open tpitman opened this issue 1 year ago • 4 comments

Description

I have a Blazor app that has docker images set up.

When I run docker-compose build the build fails with the following error:

> [internal] load metadata for mcr.microsoft.com/dotnet/aspnet:7.0-bullseye-slim-amd64: ------ failed to solve: DeadlineExceeded: DeadlineExceeded: DeadlineExceeded: mcr.microsoft.com/dotnet/sdk:7.0: failed to do request: Head "https://mcr.microsoft.com/v2/dotnet/sdk/manifests/7.0": dial tcp 204.79.197.219:443: i/o timeout

It isn't just on the dotnet/aspnet:7.0-bullseye-slim-amd64. It happens on all the images I am basing my docker images on such as sdk:7.0 and aspnet:7.0-bullseye-slim-amd64, so it doesn't seem to be specific to one image, but the site.

Configuration

dotnet 7.x (latest as of this post) MacOS 12.6 ARM64 (M1 Max) This happens during build and not while running.

Regression?

This used to work in previous versions of either Visual Studio 2022 for Mac or dotnet. The last time I did many builds for many days without issues was on dotnet 7.0.101

Other information

If I simply reboot my computer it will work for a couple builds, but then stop working again. I do not know what causes it to stop working.

tpitman avatar Mar 09 '23 21:03 tpitman

@MichaelSimons also can you help here as well, if you have any information related with this?

liveans avatar Mar 13 '23 11:03 liveans

@tpitman - when this happens, are you able to reference any other images - e.g. OS images or other images from mcr.microsoft.com. This will help pinpoint the problem. My suspicion is that this is not specific to the .NET images.

MichaelSimons avatar Mar 13 '23 13:03 MichaelSimons

You are probably correct. The only ones I am referencing are dotnet images, however, and I am not able to reproduce it on demand, so I will have to check next time it happens.

tpitman avatar Mar 13 '23 13:03 tpitman

@tpitman, if this turns out to be an issue specific to mcr.microsoft.com images, I would suggest opening an issue at https://github.com/microsoft/containerregistry/issues to see if they can help.

MichaelSimons avatar Mar 13 '23 13:03 MichaelSimons