Data Science

Switching container nodes in Docker and getting ‘no matching manifest’ error

I’ve producing content for a Kubernetes and Docker for a project I was working on recently, and I’m now just getting to blog about some of the errors that isn’t in the content. I am focused on running Windows Containers.

When I tried to pull down an image from Docker Hub, I got the following error which basically states ‘no matching manifest for windows/amd64 10.0.18362 in the manifest list entries’.

Using default tag: latest
latest: no matching manifest for windows/amd64 10.0.18362 in the manifest list entries

It turns out that the fix is quite simple: I needed to switch context in Docker Desktop to use Linux or Windows containers. In my case, I had to switch to Linux.

To find the setting, go to Docker Desktop and right click on the Docker whale in the system tray. This action will give you a menu as follows:

And that’s it! It may seem simple but it’s the sort of thing I’d forget and tear my hair over, and then be cross at myself for forgetting, so I’m blogging it here so I remember.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.