Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to pull images from microsoft #3761

Closed
devil1993 opened this issue Apr 17, 2019 · 59 comments
Closed

Unable to pull images from microsoft #3761

devil1993 opened this issue Apr 17, 2019 · 59 comments

Comments

@devil1993
Copy link

@devil1993 devil1993 commented Apr 17, 2019

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
Copy link

@pcaskey pcaskey commented Apr 17, 2019

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
Copy link
Author

@devil1993 devil1993 commented Apr 17, 2019

Am I messing something up or anything fishy going on?

@pcaskey
Copy link

@pcaskey pcaskey commented Apr 17, 2019

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

@pcaskey
Copy link

@pcaskey pcaskey commented Apr 17, 2019

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

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Apr 17, 2019

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
Copy link

@pcaskey pcaskey commented Apr 17, 2019

Ugh... Thanks for the link.

@pcaskey
Copy link

@pcaskey pcaskey commented Apr 17, 2019

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
Copy link

@pcaskey pcaskey commented Apr 17, 2019

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
Copy link
Member

@thaJeztah thaJeztah commented Apr 17, 2019

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
Copy link

@bungrudi bungrudi commented Apr 18, 2019

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

Edit: nvm this, 1709 works.

@pcaskey
Copy link

@pcaskey pcaskey commented Apr 18, 2019

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

@bungrudi
Copy link

@bungrudi bungrudi commented Apr 18, 2019

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
Copy link
Member

@thaJeztah thaJeztah commented Apr 18, 2019

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

@foss-unions
Copy link

@foss-unions foss-unions commented Apr 19, 2019

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

@pinnaman
Copy link

@pinnaman pinnaman commented Apr 19, 2019

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

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Apr 19, 2019

@pinnaman what version of Windows are you running? The version must match your Windows version (so, e.g. mcr.microsoft.com/windows/servercore:1903 if you're running Windows Server 2019)

@pinnaman
Copy link

@pinnaman pinnaman commented Apr 19, 2019

Thanks @thaJeztah , its my mistake. I was using trying to pull this image from a mac.

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Apr 19, 2019

Ah! Yes, the "for unknown" should actually be "for Linux" (it's a bug); there's a bug fix for that in Docker 19.03 (and I opened a backport for Docker 18.09 to include it in an upcoming patch release)

@elmidwill
Copy link

@elmidwill elmidwill commented Apr 29, 2019

Type winver from run, check the version and then run the correspoding version aka tag number e.g. docker run mcr.microsoft.com/windows/servercore:1607

@guilhermecgs
Copy link

@guilhermecgs guilhermecgs commented May 21, 2019

Type winver from run, check the version and then run the correspoding version aka tag number e.g. docker run mcr.microsoft.com/windows/servercore:1607

this one worked for me

@dariuszbz
Copy link

@dariuszbz dariuszbz commented Jun 3, 2019

docker pull mcr.microsoft.com/windows/nanoserver:1903 fail:
1903: Pulling from windows/nanoserver
no matching manifest for unknown in the manifest list entries

but:
docker pull mcr.microsoft.com/windows/nanoserver:1809

works fine

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Jun 3, 2019

docker pull mcr.microsoft.com/windows/nanoserver:1903 fail:
1903: Pulling from windows/nanoserver
no matching manifest for unknown in the manifest list entries

but:
docker pull mcr.microsoft.com/windows/nanoserver:1809

yes, the version you're pulling must match the version of Windows that you're running

@dariuszbz
Copy link

@dariuszbz dariuszbz commented Jun 3, 2019

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Jun 3, 2019

The versions are confusing, but Wikipedia has a nice overview; https://en.m.wikipedia.org/wiki/Windows_10

@ghost
Copy link

@ghost ghost commented Jun 6, 2019

Hi i have .Netframework app of version 4.6.1
and my host OS is Windows server 2016 standard
So which image i need for running .Netframework app of version 4.6.1.

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Jun 6, 2019

What image were you using before?

@ghost
Copy link

@ghost ghost commented Jun 6, 2019

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Jun 6, 2019

I think the dotnet images are multi-arch, so will automatically pick the right variant for your Windows version (see https://hub.docker.com/_/microsoft-dotnet-framework/, and for example, https://hub.docker.com/_/microsoft-dotnet-framework-runtime/)

@ghost
Copy link

@ghost ghost commented Jun 6, 2019

@ghost
Copy link

@ghost ghost commented Jun 11, 2019

Hi thaJeztah,
Sorry, will use another channel.
Thanks for your suggestions.

@dariuszbz
Copy link

@dariuszbz dariuszbz commented Jun 11, 2019

@adeloyedeji
Copy link

@adeloyedeji adeloyedeji commented Jun 18, 2019

Does anybody has any update on this thread, still trying to pull

microsoft/nanoserver:latest

but not working.

@dariuszbz
Copy link

@dariuszbz dariuszbz commented Jun 18, 2019

@adeloyedeji
Copy link

@adeloyedeji adeloyedeji commented Jun 19, 2019

What do you mean? Are u on windows or Linux ?

On Tue, 18 Jun 2019, 18:42 Adeloye Adedeji, @.***> wrote: Does anybody has any update on this thread, still trying to pull microsoft/nanoserver:latest but not working. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3761?email_source=notifications&email_token=AEVINAUZ6QS2MY4ZCIPWWQ3P3ENAJA5CNFSM4HGUE3F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX7NCYI#issuecomment-503239009>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEVINAVZAAOHOTRM5JIQNU3P3ENAJANCNFSM4HGUE3FQ .

On windows.

Error response from daemon: manifest for microsoft/nanoserver:latest not found

@dariuszbz
Copy link

@dariuszbz dariuszbz commented Jun 19, 2019

@adeloyedeji
Copy link

@adeloyedeji adeloyedeji commented Jun 19, 2019

Did u switch your docker to windows container ? On Wed, 19 Jun 2019, 06:02 Adeloye Adedeji, notifications@github.com wrote:

What do you mean? Are u on windows or Linux ? … <#m_-3783810049704323453_> On Tue, 18 Jun 2019, 18:42 Adeloye Adedeji, @.***> wrote: Does anybody has any update on this thread, still trying to pull microsoft/nanoserver:latest but not working. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3761 <#3761>?email_source=notifications&email_token=AEVINAUZ6QS2MY4ZCIPWWQ3P3ENAJA5CNFSM4HGUE3F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX7NCYI#issuecomment-503239009>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEVINAVZAAOHOTRM5JIQNU3P3ENAJANCNFSM4HGUE3FQ . On windows. Error response from daemon: manifest for microsoft/nanoserver:latest not found — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#3761?email_source=notifications&email_token=AEVINAVMZJS7AQWO2STWRJTP3G4U5A5CNFSM4HGUE3F2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYAWCLA#issuecomment-503406892>, or mute the thread https://github.com/notifications/unsubscribe-auth/AEVINAXOXVIO5BBPFNSL3TTP3G4U5ANCNFSM4HGUE3FQ .

Yes I did.
I never tried with Linux container in the first place.

@dariuszbz
Copy link

@dariuszbz dariuszbz commented Jun 19, 2019

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Jun 19, 2019

@adeloyedeji The microsoft/nanoserver:latest image no longer exists; see #3761 (comment), so depending on what version of Windows you're running on, you need to pull a different tag of that image, or a different image altogether.

@sjai7147
Copy link

@sjai7147 sjai7147 commented Jun 21, 2019

Goto search and find your windows version. like in windows 10 you can search "winver" command and it will show you version.

pull windows server core image by

docker pull mcr.microsoft.com/windows/servercore:1803 (your windows version)

@tasmerrick
Copy link

@tasmerrick tasmerrick commented Jun 21, 2019

I was able to get docker run mcr.microsoft.com/windows/nanoserver:1903 to download the image when I switched Docker desktop to Windows Containers (running Windows 10 Pro 1903)

@adeloyedeji
Copy link

@adeloyedeji adeloyedeji commented Jun 22, 2019

I was able to get docker run mcr.microsoft.com/windows/nanoserver:1903 to download the image when I switched Docker desktop to Windows Containers (running Windows 10 Pro 1903)

Thanks. This worked for me.

@docker-desktop-robot
Copy link
Collaborator

@docker-desktop-robot docker-desktop-robot commented Sep 20, 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

@barax
Copy link

@barax barax commented Nov 13, 2019

My Microsoft Windows [Version 10.0.14393] i can't pull nano server! i get error "Error response from daemon: manifest for microsoft/nanoserver:latest not found: manifest unknown: manifest unknown" Could i find version work my windows server 2016 or not ?

@Sanjeev4378
Copy link

@Sanjeev4378 Sanjeev4378 commented Dec 29, 2019

Problem : docker : manifest for microsoft/windowsservercore:latest not found: manifest unknown: manifest unknown
At line:1 char:1

  • docker build -t tomcat c:\java

Tried below - NO Luck

PS C:> docker pull mcr.microsoft.com/windows/servercore:ltsc2019
ltsc2019: Pulling from windows/servercore
65014b3c3121: Pulling fs layer
faf31ee0aa3d: Pulling fs layer
faf31ee0aa3d: Verifying Checksum
faf31ee0aa3d: Download complete
65014b3c3121: Verifying Checksum
65014b3c3121: Download complete
65014b3c3121: Pull complete
faf31ee0aa3d: Pull complete
Digest: sha256:4fd18320df2be163bd7a526e2b2131f9e89069fcc1a8c17e6c188e0e58e66bbd
Status: Downloaded newer image for mcr.microsoft.com/windows/servercore:ltsc2019
mcr.microsoft.com/windows/servercore:ltsc2019

PS C:> docker build -t tomcat c:\java
Sending build context to Docker daemon 315.2MB

�[91m[WARNING]: Empty continuation line found in:
RUN powershell.exe -command ./source/jre.cmd; ./source/jdk.cmd; Copy-Item c:/source/tomcat -Destination c:/tomcat -Recurse; ./source/Environmentvariable.ps1; cmd.exe /c c:/source/tomcatservice.bat; sc.exe config tomcat9 obj=L
ocalSystem start=auto; cmd.exe /c rd /S /Q c:\source
[WARNING]: Empty continuation lines will become errors in a future release.
�[0mStep 1/3 : FROM microsoft/windowsservercore
docker : manifest for microsoft/windowsservercore:latest not found: manifest unknown: manifest unknown
docker : manifest for microsoft/windowsservercore:latest not found: manifest unknown: manifest unknown
At line:1 char:1

  • docker build -t tomcat c:\java
  •   + CategoryInfo          : NotSpecified: (manifest for mi...anifest unknown:String) [], RemoteException
      + FullyQualifiedErrorId : NativeCommandError
    

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Dec 31, 2019

The microsoft/windowsservercore does not have a :latest tag, see the note in the readme on Docker Hub: https://hub.docker.com/_/microsoft-windows-servercore

Note: This repo does not publish or maintain a latest tag. Please declare a specific tag when pulling or referencing images from this repo.

In addition, those images were moved to the mcr.microsoft.com registry, and recent versions can now be found as mcr.microsoft.com/windows/servercore:<tag>

@oiliman
Copy link

@oiliman oiliman commented Mar 24, 2020

It works with: docker pull mcr.microsoft.com/windows/nanoserver:1909

See this - https://index.docker.io/_/microsoft-windows-nanoserver

@magdy880
Copy link

@magdy880 magdy880 commented Apr 17, 2020

Why is this code not working?
docker run -it --name=newapp mcr.microsoft.com/windows cmd
C:\Program Files\Docker\Docker\resources\bin\docker.exe: Error response from daemon: manifest for mcr.microsoft.com/windows:latest not found: manifest unknown: manifest unknown.
See 'C:\Program Files\Docker\Docker\resources\bin\docker.exe run --help'.

@jcklinger
Copy link

@jcklinger jcklinger commented Jun 23, 2020

I was able to get the following on Server 2019 Version 1809
docker pull mcr.microsoft.com/windows/servercore:1809
docker pull mcr.microsoft.com/windows/nanoserver:1809
docker pull mcr.microsoft.com/windows/servercore:ltsc2019

I was able to get the following on Server 2016 Version 1607
docker pull mcr.microsoft.com/windows/servercore:ltsc2016
docker pull mcr.microsoft.com/windows/servercore:1607

@jcklinger
Copy link

@jcklinger jcklinger commented Jun 23, 2020

Also found a list of tags for nanoserver here for anyone that doesn't know. Some work some don't.
https://mcr.microsoft.com/v2/windows/nanoserver/tags/list

@yule-sun
Copy link

@yule-sun yule-sun commented Jul 5, 2020

I can download the image directly from the hub.docker.com, but when i am use the private repository which configured by nexus3 as proxy repository , i cann't pull the image from the internet. I will got the error image like as
image
And the log on the Nexus3 repository is like this.
2020-07-05 07:28:28,992+0000 WARN [qtp23459870-4891] admin org.sonatype.nexus.repository.docker.internal.V2Handlers - Error: GET /v2/mcr.microsoft.com/dotnet/framework/aspnet/blobs/sha256:3889bb8d808bbae6fa5a33e07093e65c31371bcf9e4c38c21be6b9af52ad1548: 401 - org.sonatype.nexus.repository.docker.internal.V2Exception: authentication required

2020-07-05 07:28:29,320+0000 WARN [qtp23459870-4896] admin org.sonatype.nexus.repository.docker.internal.V2Handlers - Error: GET /v2/mcr.microsoft.com/dotnet/framework/aspnet/blobs/sha256:375fbabb84945635805b46a02a17ac15a3177bcaae7404cfab5f1ceb0460cb60: 401 - org.sonatype.nexus.repository.docker.internal.V2Exception: authentication required

So anyone who can help me .

@thaJeztah
Copy link
Member

@thaJeztah thaJeztah commented Jul 6, 2020

@yule-sun that looks unrelated / off-topic for this issue; best to open a support ticket with Sonatype

@docker-desktop-robot
Copy link
Collaborator

@docker-desktop-robot docker-desktop-robot commented Aug 5, 2020

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle locked

@docker docker locked and limited conversation to collaborators Aug 5, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet