Docker Community Forums

Share and learn in the Docker community.

No matching manifest for unknown in the manifest list entries

I am using Docker Desktop for windowns in Amazon’s AWS environment, so I am forced to use Windows containers because of the lack of Hyper V support. This is OK for development, but just recently I am no longer able to pull down any .net core images. I’m not a system admin, so I don’t know if something has changed in our environment to cause this. I’ve reinstalled and gone through the setup steps.

Running hello-world works fine:

docker run hello-world

My docker files that once worked no longer do. They fail with the following message:

Sending build context to Docker daemon 3.834MB
Step 1/16 : FROM microsoft/dotnet:2.2-sdk as build-env
2.2-sdk: Pulling from microsoft/dotnet
no matching manifest for unknown in the manifest list entries

Even just trying to pull the image causes a similar error:

docker pull mcr.microsoft.com/dotnet/core/sdk

Using default tag: latest
latest: Pulling from dotnet/core/sdk
no matching manifest for unknown in the manifest list entries

My version info:
Client: Docker Engine - Community
Version: 18.09.2
API version: 1.39
Go version: go1.10.8
Git commit: 6247962
Built: Sun Feb 10 04:12:31 2019
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Community
Engine:
Version: 18.09.2
API version: 1.39 (minimum version 1.24)
Go version: go1.10.6
Git commit: 6247962
Built: Sun Feb 10 04:28:48 2019
OS/Arch: windows/amd64
Experimental: false

Operating System: Windows Server 2016 Datacenter 1607 (OS Build 14393.2848)

Hi, I am also new to this forum and the Docker platform as well on 192.168.1.20. I was also facing the similar problem in the first place, that’s why I have joined it.

Definitely following for sure.

Same problem.
And I found use “microsoft/dotnet:2.2-sdk-nanoserver-sac2016” may help.
But according to https://devblogs.microsoft.com/dotnet/net-core-container-images-now-published-to-microsoft-container-registry/ Nano Server 2016 is no longer supported.
This still isn’t the perfect solution.

I had the same problem, if I switch to Linux containers then I could pull images ok.