[docker] Docker: "no matching manifest for windows/amd64 in the manifest list entries"

I use Docker on Windows, and when I tried to pull a PHP image with this command

$ docker pull php

I got this message:

Using default tag: latest
latest: Pulling from library/php no matching manifest for windows/amd64 
        in the manifest list entries

How can I fix this problem?

I had this same issue on Windows 10. I bypassed it by running the Docker daemon in experimental mode:

1. Right click Docker icon in the Windows System Tray
2. Go to Settings
3. Daemon
4. Advanced
5. Set the "experimental": true
6. Restart Docker

There could be many reasons for this error. But most obvious reason for this error is using Windows Container in Linux Container Mode or vise versa.

1. Click Docker Icon in System Tray In Context Menu
2. Click "Switch to Window/Linux Container"
3. Option Click Switch Button in Switch Dialog
4. It may take little time
5. Make Sure Docker is Running State Now

You are in Windows container mode. So if you're not sure that the image you want to pull is built for the Windows architecture, you need to switch to Linux containers.

In my case it was that the Windows OS version I was on did not support the tag I was trying to pull. Utilizing an older tag allowed me to get this to work.

Specifically:

docker pull mcr.microsoft.com/windows/nanoserver:1903 errored

docker pull mcr.microsoft.com/windows/nanoserver:1803-amd64 worked

Another possible way to do this:

In system tray, right click on docker icon, then click on Switch to Linux containers.

(Docker for Windows, Community Edition, version 18.03.1)

Version: Windows 10

Step 1: Right click Docker instance and Go to Settings

Step 2: Basic to Advanced and setting the "experimental": true

Step 3: Restart Docker

Step 4: To install dockerfile is successful( ex: docker build -t williehao/cheers2019 . )

I solved this in Windows 10 by running in admin Powershell:

cd "C:\Program Files\Docker\Docker"

And then:

./DockerCli.exe -SwitchDaemon

You need to pull with the Linux platform first, then you can run on Windows:

docker pull --platform linux php
docker run -it php

See blog post Docker for Windows Desktop 18.02 with Windows 10 Fall Creators Update.

This looks like "docker pull" fails in windows 10 #1100

If adding --experimental does not work, consider re-installing docker for windows.

This may not only happen due to windows containers!

Today all Node.Js docker images are not pullable. Always check the image you are trying to pull before.

Related Github-Issue

I was getting this error in my Azure DevOps pipeline.

Step 1/7 : FROM nginx:alpine
alpine: Pulling from library/nginx
no matching manifest for windows/amd64 10.0.14393 in the manifest list entries
##[error]C:\Program Files\Docker\docker.exe failed with return code: 1
##[section]Finishing: Build an image

The problem was I had selected the Hosted VS2017 instead of the Hosted Ubuntu. After changing the same as follows, the build was successful.

Hope it helps.

Right click Docker instance Go to Settings Daemon Advanced Set the "experimental": true Restart Docker

 {
      "registry-mirrors": [],
      "insecure-registries": [],
      "debug": true,
      "experimental": true
    }

Deprecating the ‘latest’ tag

We are deprecating the ‘latest’ tag across all our Windows base images to encourage better container practices. At the beginning of the 2019 calendar year, we will no longer publish the tag ; We’ll yank it from the available tags list.

We strongly encourage you to instead declare the specific container tag you’d like to run in production. The ‘latest’ tag is the opposite of specific; it doesn’t tell the user anything about what version the container actually is apart from the image name. You can read more about version compatibility and selecting the appropriate tag on our container docs .

https://techcommunity.microsoft.com/t5/containers/windows-server-2019-now-available/ba-p/382430#

Consider the applications that you are pulling - are they Windows based? If not, you need to run a Linux container.

Without using the experimental mode, you can only use Docker in one style of container vs the other. If you activate the experimental mode as mentioned above, you can use Windows and Linux containers as required by the applications you are pulling in the compose file.

Key note: Experimental - still in development by Docker.

I had the same problem to run Windows IIS image using docker for Windows. Reading the Mohammad Trabelsi response above I realised that to solve my problem I needed to switch my containers (on docker) for Windows containers.

To do this:

1. Right click Docker instance
2. Select "Switch to Windows containers..."

docker run mcr.microsoft.com/windows/servercore:ltsc2016

try the above command. what you are pulling should be compatible with the underlying windows version you are in. above will work if you are in windows server 2016.

follow this thread for more info

https://github.com/docker/for-win/issues/3761

For me, it is because of access denied to C:\ProgramData\Docker\config\daemon.json After I fixed it now it works. You can try to switch to Linux containers and switch back. If there is no problem with the switching, then it works with the access permission.

On Windows you must edit the file daemon.json or windows-daemon-options.json, the default location of the configuration file on Windows is %programdata%\docker\config\daemon.json or %programdata%\docker\resources\windows-daemon-options.json

The optional field features on the json file, allows users to enable or disable specific daemon features. Example: {"features":{"buildkit": true}} enables buildkit as the default docker image builder.

In my case I had to update windows first, after that the problem has gone.

In Docker:

1. go to Settings
2. go to Docker Engine
3. change experimental to true
4. press Apply and Restart

.

The reason it is showing this message because it is unable to find Linux containers as running. So, make sure you switch from windows to linux containers before running it.