我已经运行了几天,每天很多次,并且没有改变我的DOCKERFILE或docker-compose.yml。一小时前我突然发现:
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
我尝试过的事情:
运行it again
docker rm -f $(docker ps -a -q)
docker login
的
这是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"]
我怎样才能让我的构建重新开始工作?
发布于 2021-04-01 22:02:39
mcr.microsoft.com现在倒了
我在拉时收到了几个不同的错误:
% 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
发布于 2022-01-27 15:23:45
为我工作的解决方案是删除. .docker/config.json通过运行
rm ~/.docker/config.json
那么docker-compose up your-services
应该能工作
发布于 2021-12-01 01:17:01
在我的例子中,是公司VPN导致了这个问题。一旦我禁用了VPN,它就能正常工作。我承认不是真正的解决办法。您可以在此命令运行期间禁用VPN并启用它。
https://stackoverflow.com/questions/66912085
复制相似问题