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

Cannot pull some of the Nanoserver and WindowsServerCore image tags #5

Closed
dbramhallconcentrix opened this issue Jul 22, 2019 · 23 comments

Comments

@dbramhallconcentrix
Copy link

When I try to download a lot of the Windows Server Core and Nano Server images, I get the below error.

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

Same issue with mcr.microsoft.com images/tags

Same issue as the below
docker/for-win#3761

Docker About

@rotata
Copy link
Member

rotata commented Jul 23, 2019

could you please provide some diagnostic logs for your issue, you can find more information on the steps to get the logs here https://docs.microsoft.com/en-us/azure/container-registry/container-registry-faq#enable-and-get-the-debug-logs-of-the-docker-daemon.
Also, how many images are you trying to download?

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 23, 2019 via email

@bariscaglar
Copy link
Contributor

I have tried a few of them (1903, 1903-KB4505057, 1809) from nanoserver and all three worked. Which tags are you having trouble with?

@bariscaglar
Copy link
Contributor

bariscaglar commented Jul 23, 2019

If you're trying "latest" tag, it won't work because the Windows team decided to discontinue that tag due to ambiguity it carried. You'll see that it doesn't exist in the full tag listing. This article has more on that.

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 23, 2019 via email

@bariscaglar
Copy link
Contributor

I'm sorry, I don't think your image uploaded correctly. This is all I am seeing:

Yep, I saw the article about no more latest. I am not trying to pull latest tags for any MS docker images. Below is an image of the tags I tried today.

[cid:image001.png@01D54165.FFACE180]

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 23, 2019 via email

@mamezgeb
Copy link
Member

mamezgeb commented Jul 23, 2019

Hi there, we on the GitHub issue view can't see the image you're attaching. Could you use the GitHub issue UI here and attach the image using the comment system? Or alternatively, list out the tags that are failing? I'm in alignment with Baris' prior comments.

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 24, 2019 via email

@mamezgeb
Copy link
Member

mamezgeb commented Jul 24, 2019

When you run docker info, what shows up by Kernel Version and Operating System?

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 24, 2019 via email

@bariscaglar
Copy link
Contributor

One reason I could find why people run into this issue is their Docker installation was set to "Linux Containers".

That said, on my end, it all works:

docker pull mcr.microsoft.com/windows/servercore:1809
1809: Pulling from windows/servercore
65014b3c3121: Already exists 02a4c14ecf32: Pull complete Digest: sha256:0193dba5d3c7f3c0e23ea956a62f77122585ddb2295435895ecc214122f47475
Status: Downloaded newer image for mcr.microsoft.com/windows/servercore:1809
mcr.microsoft.com/windows/servercore:1809

The rest of the output is similar. The diagnostics on your end could really help, unless @mamezgeb can see what's wrong from the version output above.

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 24, 2019 via email

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 24, 2019 via email

@bariscaglar
Copy link
Contributor

Could you be trying to pull versions that are higher than your OS version? Are the ones that work all lower version tags?

I think Rohit's original message contained the instructions on getting diagnostics: https://docs.microsoft.com/en-us/azure/container-registry/container-registry-faq#enable-and-get-the-debug-logs-of-the-docker-daemon.

Also, your docker tooling version is old. Before proceeding, I suggest you upgrade to latest.

Finally, I think Markos was asking for the 'docker info'. What you pasted is 'docker version' output.

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 24, 2019 via email

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 24, 2019 via email

@bariscaglar
Copy link
Contributor

When you say docker tooling, do you mean my docker desktop version? I just tried to upgrade and docker responded by saying I was up to date.

You are actually quite right. You have the latest stable version. On my machine, I am on an "Edge Release", which is why my version is 19.xxxx while yours is 18.xxxx.

@bariscaglar
Copy link
Contributor

Kernel Version: 10.0 17134 (17134.1.amd64fre.rs4_release.180410-1804)

I think this is the reason why you are unable to pull 1809 images. This StackOverflow has a an answer to the issue similar to yours.

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 24, 2019 via email

@bariscaglar
Copy link
Contributor

bariscaglar commented Jul 25, 2019

Have you had success with 1803 on Nano as well?

@dbramhallconcentrix
Copy link
Author

dbramhallconcentrix commented Jul 25, 2019 via email

@bariscaglar
Copy link
Contributor

Looks like this issue is resolved. Please feel free to reach out to us if you run into further problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants