'Why is docker-compose failing with ERROR internal load metadata suddenly?

I've been running docker-compose build for days, many times per day, and haven't changed my DOCKERFILEs or docker-compose.yml. Suddenly an hour ago I started getting this:

Building frontdesk-api
failed to get console mode for stdout: The handle is invalid.
[+] Building 10.0s (3/4)
 => [internal] load build definition from Dockerfile                       0.0s
[+] Building 10.1s (4/4) FINISHED
 => [internal] load build definition from Dockerfile                       0.0s
 => => transferring dockerfile: 32B                                        0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => ERROR [internal] load metadata for mcr.microsoft.com/dotnet/sdk:5.0.  10.0sailed to do request: Head https://mcr.microsoft.com/v2/dotnet/sdk/manifests/5.0.201-buster-slim: dial tcp: lookup mcr.microsoft.com on 192.168.65.5:53:
 => [internal] load metadata for mcr.microsoft.com/dotnet/aspnet:5.0-bust  0.0s
------
 > [internal] load metadata for mcr.microsoft.com/dotnet/sdk:5.0.201-buster-slim:
------
ERROR: Service 'frontdesk-api' failed to build

Things I've tried:

Running it again
docker rm -f $(docker ps -a -q)
docker login
Different SDK image

Here is the DOCKERFILE:

FROM mcr.microsoft.com/dotnet/aspnet:5.0-buster-slim AS base
WORKDIR /app
EXPOSE 80
EXPOSE 443

FROM mcr.microsoft.com/dotnet/sdk:5.0.201-buster-slim AS build
WORKDIR /app
# run this from repository root
COPY ./ ./ 
#RUN ls -lha .

RUN echo 'Building FrontDesk container'

WORKDIR /app/FrontDesk/src/FrontDesk.Api
#RUN ls -lha .
RUN dotnet restore

RUN dotnet build "FrontDesk.Api.csproj" -c Release -o /app/build

FROM build AS publish
RUN dotnet publish "FrontDesk.Api.csproj" -c Release -o /app/publish

FROM base AS final
WORKDIR /app
COPY --from=publish /app/publish .
ENTRYPOINT ["dotnet", "FrontDesk.Api.dll"]

How can I get my build working again?

docker docker-compose

Solution 1:^[1]

mcr.microsoft.com is down at the moment

I'm receiving several different errors when pulling:

% docker pull mcr.microsoft.com/dotnet/sdk:5.0
Error response from daemon: Get https://mcr.microsoft.com/v2/: Service Unavailable

% docker pull mcr.microsoft.com/dotnet/sdk:5.0
5.0: Pulling from dotnet/sdk
received unexpected HTTP status: 500 Internal Server Error

Solution 2:^[2]

the solution that worked for me is to delete the .docker/config.json by running

rm  ~/.docker/config.json

then docker-compose up your-services should work

Solution 3:^[3]

In my case, it was corporate VPN that caused this issue. Once I disabled the VPN, it worked fine. Not really a solution, I admit. You could disable the VPN for the duration of this command run and enable it back.

Solution 4:^[4]

For linux

Step 1: sudo vi ~/.docker/config.json

You will see something like this:

    {
      "credsStore": "desktop.exe"
    }

Step 2: Update credsStore to credStore

Step 3: Run your services docker-compose up your-services

Windows:

Step 1: Go to C:\Users\Name\.docker

Step 2: Open config.json

Step 3: Update credsStore to credStore

Step 4: Run your services docker-compose up your-services

Solution 5:^[5]

Could it be the is getting the wrong arch/platform to build the image. Try specifying one in the command:

docker build -t auth:1.0.0 --platform=linux/arm64 .

getting the current arch

arch

Solution 6:^[6]

Happened the same to me after adding custom nameservers.

   [network]
   generateResolvConf = false

I reverted that line on

/etc/wsl.conf

and after doing wsl.exe --shutdown on the powersell and restart again docker, it worked fine again.

Solution 7:^[7]

I had:

ERROR [internal] load metadata for docker.io/library/python:3.7-slim

Running the exact same command again helped, I swear.

Solution 8:^[8]

I think this has to do with issues trying to load the meta data of the image specified in the dockerfile from the dockerhub or the container repository of your choice. a quick fix is to check if your internet is up or you have necessary access. this is what resolve it for me.

Solution 9:^[9]

It was proxy settings for me. I had proxy enabled in docker desktop. Disabling worked for me.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution	Source
Solution 1	Joe Phillips
Solution 2	Carlos
Solution 3	Vijayanand Settin
Solution 4	bguiz
Solution 5	Luillyfe
Solution 6	beerLantern
Solution 7	diana_before
Solution 8	user12575927
Solution 9	Karan Rahar

'Why is docker-compose failing with ERROR internal load metadata suddenly?

Solution 1:[1]

Solution 2:[2]

Solution 3:[3]

Solution 4:[4]

Solution 5:[5]

Solution 6:[6]

Solution 7:[7]

Solution 8:[8]

Solution 9:[9]