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

Question

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?

To help others, I got into this error while creating image for linux as base OS.... Reason for this error was it was set for windows containers so then I switched to Linux containers then it started working... — Abhishek Jain, Jan 19 '19 at 07:13
Also, for posterity: I got this building a Windows container. Even though I switched to Windows, it appears to have switched back to Linux. Changing it back to Windows fixed the problem. — John MacIntyre, Jun 25 '19 at 18:00

score 376 · Accepted Answer · edited Jan 01 '20 at 17:21

376

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

Right click Docker icon in the Windows System Tray
Go to Settings
Daemon
Advanced
Set the "experimental": true
Restart Docker

edited Jan 01 '20 at 17:21

Community

1
1

answered Jun 27 '18 at 20:39

benscabbia

17,592
13
51
62

Besides the previous answers, I also had to remove "read only" attribute of my C:\WINDOWS\System32\drivers\etc\hosts.etc – Thiago Custodio Mar 27 '19 at 14:50
9

On Windows, you can locate the config file directly at '%programdata%\docker\config\daemon.json' and set the attributes there. – NemyaNation Aug 07 '19 at 09:59
5

This worked for me and I was just wondering why does this work? What is experimental for? – Nic Parmee Aug 22 '19 at 11:43
4

If you're running docked (daemon) from standalone binary use `--experimental` feature – Anwar Sep 01 '19 at 17:12
Couldn't edit via graphic interface. Had to use **Cmder as administrator** and run commands `cd C:\ProgramData\Docker\config` and `nano daemon.json` to set **experimental** value to **true**, and then restart Docker (right click on the icon near the clock at right bottom - click on the arrow to show hidden icons) – Patrick Apr 18 '20 at 11:28
2

setting "experimental": true has any security issues? do I need to revert back once operation completed? – kudlatiger May 10 '21 at 11:39
2

so what is being *experimented*? – Lei Yang Mar 23 '22 at 09:51
thanks this worked for me, nothing else on the net was working, come on docker. – petey m Jul 11 '22 at 20:02

score 319 · Answer 2 · answered Aug 18 '19 at 22:59

319

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.

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

answered Aug 18 '19 at 22:59

Imran Javed

11,779
2
16
17

16

It solved my problem about "no matching manifest for windows/amd64" – winlinux Sep 03 '19 at 12:49
2

It worked for me with the issue 'no matching manifest for windows/amd64 10.0.17134 in the manifest list entries' – Amna Dec 03 '19 at 09:55
3

This answer is irrelevant for Windows Container. It only works if your container requirement is Linux Container. Please refer to @benscabbia's answer. – junnyea Jul 28 '20 at 10:57
Hi @junnyea, I tried to explain for both cases, so if you are on Windows Container in user, then Linux Containers Settings will not work and you may have to move to Windows Containers Settings, and vise versa. – Imran Javed Jul 29 '20 at 12:34
1

For my case, I need to run it in a Windows architecture. There is no point to switch to a Linux container. It will be more relevant if the solution given was not switching between container. – junnyea Aug 03 '20 at 06:30
2

If you can't find the system tray icon, this command will do it, on PowerShell `& $Env:ProgramFiles\Docker\Docker\DockerCli.exe -SwitchDaemon .` See here https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/set-up-environment?tabs=dockerce – aviggiano Oct 07 '22 at 21:03
1

Thanks! I was trying to run a Windows container off of the `node` image, and there isn't a Windows version of the `node` image, apparently. This answer helped me further: https://stackoverflow.com/a/72583505/2552903 – tolache Oct 13 '22 at 17:59

score 108 · Answer 3 · edited Jul 24 '18 at 08:35

108

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.

edited Jul 24 '18 at 08:35

Peter Mortensen

30,738
21
105
131

answered Mar 18 '18 at 15:27

Ahmad Hassan

1,181
1
7
6

1

The alternative (that I also found to be working) is in [chuck's answer](https://stackoverflow.com/questions/48066994/docker-no-matching-manifest-for-windows-amd64-in-the-manifest-list-entries/49785458#49785458) – Peter Mortensen Jul 24 '18 at 11:44
once it failures to switch ? it's a work around way – Tiago Medici Nov 15 '19 at 09:37
1

If you switch to Linux Containers will you then be able to host Windows applications within Docker? For example using IIS and MySQL on the same Docker instance. – webworm Feb 10 '20 at 00:03
@webworm since there's also MySQL for Windows, why use a Linux version when you want to mix it with IIS and not just use its Windows version? – George Birbilis Apr 20 '20 at 00:52

score 74 · Answer 4 · answered Jul 30 '19 at 18:39

74

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

answered Jul 30 '19 at 18:39

joedragons

2,505
21
21

2

This! Microsoft changed there something compared to the old images (servercore/nanoserver). Now, you need to lookup the windows version of the system for which you're deploying to and choose the base image accordingly. – JustCoding Oct 25 '19 at 10:51
1

Nice answer! This worked for me on Windows 10 following this tutorial https://learn.microsoft.com/en-us/virtualization/windowscontainers/quick-start/run-your-first-container – user1299379 Feb 03 '20 at 22:35
It also worked for me. But does it mean that I need to have this approach when I pull every image, for eg hello-world? – Mandroid Apr 08 '20 at 06:26
@Mandroid I would be interested in your findings but some images seemed to work and some didn't in my case, so I'd guess it's very setup specific. e.g. if you have one Windows patch may vary from another. – joedragons Apr 21 '20 at 20:10
Use `winver` to make sure that the windows version of your host machine is newer or equal to the version in the image. – cowlinator Apr 28 '20 at 00:07
In order to pull windows server on windows 10, I had to go back to the earliest tag: win10-21h1-preview – dudeNumber4 Oct 17 '22 at 14:41

Willie Cheng · Answer 5 · 2021-09-29T05:13:48.880

63

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 . )

edited Sep 29 '21 at 05:13

answered Dec 13 '19 at 16:23

Willie Cheng

7,679
13
55
68

score 39 · Answer 6 · answered Oct 07 '18 at 06:08

39

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)

answered Oct 07 '18 at 06:08

tomab

2,061
5
27
38

score 23 · Answer 7 · answered Apr 23 '20 at 00:40

23

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

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

And then:

./DockerCli.exe -SwitchDaemon

answered Apr 23 '20 at 00:40

Jared Zena

340
3
6

This can also be done by right clicking the Docker Desktop icon and selecting `Switch to Windows Containers` / `Switch to Linux Containers` as required. NB: You'll still get issues if the Windows image you're installing is ahead of your host version of windows (e.g. see OS Version column: https://hub.docker.com/_/microsoft-windows) – JohnLBevan Feb 11 '21 at 08:21

score 17 · Answer 8 · edited Nov 20 '22 at 18:31

Update for Windows 10 20H2

Go to Docker configurations
Go to the Docker Engine tab
Change the line "experimental": false to "experimental": true
Restart Docker using the Apply & Restart button

You can also modify the configuration file manually by opening it with your favorite code editor (Visual code, Notepad++...), like this for example:

# BACKUP Your file with PowerShell
Copy-Item -Path C:\ProgramData\Docker\config\daemon.json -Destination C:\ProgramData\Docker\config\daemon.json.backup

# Open the file with Visual Code
code C:\ProgramData\Docker\config\daemon.json

Or change the string directly with Powershell

# Set Path in variable
$FILE = "C:\ProgramData\Docker\config\daemon.json"

# Replace '"experimental": false' to '"experimental": true'
(Get-Content -Path $FILE) -replace '"experimental": false','"experimental": true' | Set-Content -Path $FILE

# Check the file content
type $FILE

Output example

PS C:\WINDOWS\system32> type $FILE
{
  "registry-mirrors": [],
  "insecure-registries": [],
  "debug": false,
  "experimental": true
}

After your need restart the Docker daemon

PS C:\WINDOWS\system32> Restart-Service docker

Check the status of the service

PS C:\WINDOWS\system32> Get-Service docker
Status   Name               DisplayName
------   ----               -----------
Running  docker             Docker Engine

score 14 · Answer 9 · edited Jul 24 '18 at 11:51

14

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.

edited Jul 24 '18 at 11:51

Peter Mortensen

30,738
21
105
131

answered Apr 11 '18 at 22:47

chuck

315
3
8

Yes, the `--platform` flag works too. Though it may redownload stuff. – Peter Mortensen Jul 24 '18 at 11:41
"--platform" is only supported on a Docker daemon with experimental features enabled – Michal Špondr Nov 08 '19 at 07:28

score 9 · Answer 10 · answered Jan 24 '21 at 15:06

9

In Docker:

go to Settings
go to Docker Engine
change experimental to true
press Apply and Restart

.

answered Jan 24 '21 at 15:06

SeyedPooya Soofbaf

2,654
2
29
31

score 8 · Answer 11 · edited Feb 04 '20 at 07:32

8

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

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

edited Feb 04 '20 at 07:32

Nicolás Alarcón Rapela

2,714
1
18
29

answered Jan 02 '18 at 22:35

VonC

1,262,500
529
4,410
5,250

1

Adding "experimental: true" didn't work for me, so I thought I'd try switching to the Linux container before re-installing docker and it worked. – yoges nsamy Aug 16 '18 at 02:35
On Windows enviroment, also check if Hyper-V Virtual Machine Management service is running, then after installing docker, switch it to Linux containers mode. – Junior Mayhé Feb 09 '19 at 17:33
1

Adding `experimental` works , thanks... Why is that so ? – Angshuman Agarwal Apr 12 '20 at 15:06
@AngshumanAgarwal Using experimental features (https://docs.docker.com/docker-for-windows/#command-line) adds drivers (https://github.com/docker/cli/blob/master/experimental/README.md#current-experimental-features) which might be needed for using Docker for Windows. – VonC Apr 12 '20 at 15:28

score 5 · Answer 12 · edited Apr 17 '23 at 12:17

5

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

edited Apr 17 '23 at 12:17

malat

12,152
13
89
158

answered Jul 02 '19 at 06:48

Sithija Piyuman Thewa Hettige

1,768
20
26

This is true for `ltsc2019` vs `ltsc2022` as well. One of my computers (newer) could run 22, but my other computer couldn't. – daevski Mar 31 '22 at 19:37

score 5 · Answer 13 · answered Dec 05 '19 at 22:10

5

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

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

answered Dec 05 '19 at 22:10

harun ugur

1,718
18
18

score 5 · Answer 14 · answered Apr 17 '21 at 19:59

This just happened to me after I upgraded Docker Desktop (previously configured with WSL2 integration.)

In case you ran into this after an upgrade, just FYI that I had to do the following:

Run PowerShell in Administrator (elevated) mode and execute the following commands:

cd "C:\Program Files\Docker\Docker"
./DockerCli.exe -SwitchDaemon

If you don't do this, you might not be able to open up the Settings tab on Docker Desktop.

Then, you need to switch to Linux Containers in Settings (by unchecking "Use the WSL2 based engine"), then restart.

At this point, just run a quick test that downloads an image and runs a container off it, to see if that solves the issue:

docker run --rm -ti alpine:latest uname -a
Linux 2b08b155a042 5.4.72-microsoft-standard-WSL2 #1 SMP Wed Oct 28 23:40:43 UTC 2020 x86_64 Linux

From there, if you were running with WSL2 integration, simply go back to the Settings screen and undo the selection we did in step number two (which will restart docker.)

At that point, you will see all images and stopped containers you had prior to the upgrade.

score 5 · Answer 15 · answered Jun 15 '21 at 16:31

I have encountered this error when I started learning docker and my understanding of this scenario is below:

why you hit this issue: Because you're referring the image of Linux based and you're currently using windows base platform to run/ build docker image.

Resolution: Short answer: Either switch your current platform to Linux mode or pull the windows based image. Here is the list of possible options:

Switch to Linux Containers as the error is "no matching manifest for windows/amd64"
Set the docker environment "experimental": true.
Pull the image specific to a platform e.g. docker pull --platform {linux/Windows} {image-name}

score 4 · Answer 16 · answered Feb 27 '20 at 08:21

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#

score 3 · Answer 17 · answered Oct 08 '18 at 18:27

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.

score 3 · Answer 18 · answered Nov 28 '18 at 14:21

3

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

answered Nov 28 '18 at 14:21

FabianTe

516
4
22

score 3 · Answer 19 · answered Apr 18 '19 at 17:41

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:

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

score 3 · Answer 20 · answered Jun 25 '19 at 13:50

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.

score 2 · Answer 21 · answered Apr 19 '20 at 12:58

2

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

answered Apr 19 '20 at 12:58

Legends

21,202
16
97
123

Yes! If your version of Windows has gone out of service, you will get this error message. Running Update will solve it! – Jason D Jan 14 '21 at 17:58

score 2 · Answer 22 · answered Jan 13 '22 at 07:11

2

Make sure you aren't trying to use Linux/WSL to pull a Windows image.

Use a Powershell terminal instead.

answered Jan 13 '22 at 07:11

Samuurai

375
2
13

This issue could be with terminal what you are using. If you use Git bash or Linux/WSL you will get this error. – Vijay Sep 08 '22 at 10:45

GoYun.Info · Answer 23 · 2020-04-02T19:28:30.007

1

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.

edited Apr 02 '20 at 19:28

answered Aug 01 '19 at 15:23

GoYun.Info

1,356
12
12

Tiago Medici · Answer 24 · 2019-10-28T18:53:07.563

1

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.

edited Oct 28 '19 at 18:53

answered Oct 28 '19 at 18:44

Tiago Medici

1,944
22
22

on windows server 2019 run this: $configfile =@" { "experimental":true } "@ $configfile|Out-File -FilePath c:\Programdata\docker\config\daemon.json -Encoding ascii -Force restart-Service docker – Nicolae Lupei Dec 15 '20 at 10:33

score 0 · Answer 25 · answered Sep 28 '19 at 04:39

0

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.

answered Sep 28 '19 at 04:39

Udit Gandhi

337
4
6

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

25 Answers25

Update for Windows 10 20H2

Linked

Related