Unable to pull images from microsoft

[devil1993]

I am new to docker and trying to set up a container on a Windows Server 2016 instance(14392.2906). Docker is running with windows container. But when I am trying to pull any of the images, I am getting the same error saying:
Error response from daemon: manifest for microsoft/windowsservercore:latest not found.

I tried to pull node as well, getting error as:
no matching manifest from unknown in the manifest list entries.

However when I tried
docker pull python
it started downloading, I did not complete the download as I didn't require it.

Expected behavior

download the image

Actual behavior

getting issues with manifest entries as described above.

Information

docker search microsoft

runs with following results:

microsoft/dotnet
microsoft/mssql-server-linux
microsoft/aspnet
microsoft/windowsservercore
microsoft/aspnetcore
microsoft/nanoserver
microsoft/iis
microsoft/mssql-server-windows-developer
microsoft/aspnetcore-build
microsoft/azure-cli
microsoft/powershell
microsoft/vsts-agent
microsoft/dynamics-nav
microsoft/dotnet-samples
microsoft/bcsandbox
microsoft/mssql-tools
microsoft/oms
microsoft/cntk
microsoft/wcf
microsoft/dotnet-nightly
microsoft/dotnet-framework-build
microsoft/mmlspark
microsoft/service-fabric-reverse-proxy
microsoft/aspnetcore-build-nightly
microsoft/cntk-nightly

version is as below:

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: true

Steps to reproduce the behavior

same issue is found for the following images:
microsoft/nanoserver

[pcaskey]

Same issue here. And notice that windowsservercore does not show as an automated build.

Not listed in the output of this command: docker search --filter "is-automated=true" microsoft

[devil1993]

Am I messing something up or anything fishy going on?

[pcaskey]

something fishy IMHO. My build has been working for many months, except when I tried a new build today.

[pcaskey]

Many of their images are currently broken like this. But this one works:
docker pull microsoft/aspnet

[thaJeztah]

Microsoft deprecated the :latest images, and had them removed from Docker Hub; https://techcommunity.microsoft.com/t5/Containers/Windows-Server-2019-Now-Available/ba-p/382430

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.

So, it's not a bug, but I can definitely feel the pain of that change (I'm in the process of updating various GitHub repositories to make them build again 😞)

[pcaskey]

Ugh... Thanks for the link.

[pcaskey]

still having same problem though. I copied/paste this from their docker hub page (https://hub.docker.com/_/microsoft-windows-servercore)

PS C:> docker pull mcr.microsoft.com/windows/servercore:ltsc2019
ltsc2019: Pulling from windows/servercore
no matching manifest for unknown in the manifest list entries

[pcaskey]

Probably this:
"Windows requires the host OS version to match the container OS version. If you want to run a container based on a newer Windows build, make sure you have an equivalent host build. Otherwise, you can use Hyper-V isolation to run older containers on new host builds."

I wish Microsoft would just stop, well, being Microsoft...

[thaJeztah]

Yes, when running with process-isolation, the version must match the Windows kernel version you're running on. Unlike Linux, the Windows kernel does not have a stable API, so container images running on Windows must have libraries that match the kernel on which they will be running to make it work (which is also why those images are a lot bigger than Linux images).

[bungrudi]

anyone know a working tag for microsoft/nanoserver?
I tried 1809 to no succeed.

Edit: nvm this, 1709 works.

[pcaskey]

FWIW, this should work: docker pull mcr.microsoft.com/windows/nanoserver:1809

[bungrudi]

FWIW, this should work: docker pull mcr.microsoft.com/windows/nanoserver:1809

C:\U\Rudi Adianto> docker pull mcr.microsoft.com/windows/nanoserver:1809
1809: Pulling from windows/nanoserver
no matching manifest for unknown in the manifest list entries

No luck :\

[thaJeztah]

The nano-server images for Windows Server 2016 were marked EOL and they had them removed from Docker Hub

[foss-unions]

This command worked for me. thanks so much @thaJeztah !
docker pull mcr.microsoft.com/windows/servercore:ltsc2016

[pinnaman]

The above command does not work. Gives me the below info:
docker pull mcr.microsoft.com/windows/servercore:ltsc2016
ltsc2016: Pulling from windows/servercore
no matching manifest for unknown in the manifest list entries