none
Failed to pull Windows Server 2019 container image RRS feed

  • Question

  • First of all, I am really happy to use the brand new OS, Windows Server 2019!

    I have tried to pull Windows Server 2019 container image but I failed... I did the following steps in my lab. Do you have any good idea?

    Environment

    • Container host: Windows Server 2019 Datacenter (I have got it from MSDN)
    • Container host is running on Windows Server 2012 R2 Hyper-V
    • My lab has a proxy server to access to the Internet

    What I did

    1. Install Windows Server 2019 on a virtual machine.
    2. Set HTTP_PROXY and Path to Environment Variables.
    3. Start Internet Explorer 11 and edit proxy parameter.
    4. Run the following command to enable Containers role and install Docker. And restart OS.
      PS> Install-Module -Name DockerMsftProvider -Repository PSGallery -Force
      PS> Install-Package -Name docker -ProviderName DockerMsftProvider
      https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/deploy-containers-on-server
    5. Run "docker search" to check if my machine can access to the Internet.
      C:\Users\Administrator>docker search microsoft
      NAME DESCRIPTION STARS OFFICIAL AUTOMATED
      microsoft/dotnet Official images for .NET Core and ASP.NET ... 1184 [OK]
      microsoft/mssql-server-linux Official images for Microsoft SQL Server o... 974
      microsoft/aspnet ASP.NET is an open source server-side Web ... 778 [OK]
      :
      (snip)
    6. Then, run docker pull command but failed... How should I do to shake hands with Microsoft?
      C:\Users\Administrator>docker pull mcr.microsoft.com/windows/servercore:ltsc2019
      ltsc2019: Pulling from windows/servercore
      error pulling image configuration: Get https://mcrea0.cdn.mscr.io/b29889755b1f4e46b6b44eb3182530c5-0joxcrfl25//docker/registry/v2/blobs/sha256/a2/a25dc097c6330ee730842633ca668121169904fe613b0bbd45c588ab35079371/data?P1=1538615279&P2=1&P3=1&P4=iWVVhGO31V2CZQ4nxDRBQlnliWeRXYIRPLBd%2B%2F4eH%2BE%3D&se=2018-10-04T01%3A07%3A59Z&sig=oVvL3dGfvqMa3ImfYGDopFGgSqz3kkd7k17ZtI92AAo%3D&sp=r&sr=b&sv=2016-05-31®id=b29889755b1f4e46b6b44eb3182530c5: remote error: tls: handshake failure

    Thursday, October 4, 2018 12:49 AM

All replies

  • Greetings,

    You can check the tag list here. You may pull microsoft/winndowsservercore:ltsc2019 when it is available.

    https://store.docker.com/images/windowsservercore/plans/1e9acba1-c879-49b0-9109-7cfcf820a47a?tab=tags

    Or can you check the tag in mcr?



    Sic Parvis Magna


    Thursday, October 4, 2018 5:45 AM
  • Thank you for your reply.

    Yes, I have checked the following site how to get Windows Server 2019 container image.
    https://hub.docker.com/r/microsoft/windowsservercore/

    Supported Windows Server 2019 (Long Term Support Channel) Tags
    docker pull mcr.microsoft.com/windows/servercore:ltsc2019

    I have tried it but failed...


    Thursday, October 4, 2018 10:21 AM
  • Ah! mcr.microsoft.com is running on Azure, isn't it? If so, this issue may be caused by my own network.

    OK, I'll try do the same steps on Azure VM.

    Friday, October 5, 2018 1:04 AM
  • Greetings,

    You may turn off proxy for another try.



    Sic Parvis Magna

    Friday, October 5, 2018 1:24 AM
  • Hi there,

    I also cannot pull the LTSC 2019 or 1809 images from mcr.microsoft.com.

    I get the following error:

    Error response from daemon: manifest for mcr.microsoft.com/windows/servercore:ltsc2019 not found

    Error response from daemon: manifest for mcr.microsoft.com/windows/servercore:1809 not found

    I do not run a proxy and have direct internet access.

    Any ideas?

    Cheers,

    Ben

    Monday, October 15, 2018 4:56 AM
  • They (pardon the pun) pulled the images after they pulled windows 10 and server 2019 because of the loss of data issues that were reported.

    Since Windows 10 1809 and Server 2019 is now available again, they haven't pushed new images to the registry yet. Not sure why...

    Regards
    Dewald

    • Proposed as answer by Benage Tuesday, October 16, 2018 12:27 AM
    Monday, October 15, 2018 3:05 PM
  • Thanks Dewald, really appreciate your reply! I was tearing my hair out for the last few days trying to figure it out haha.

    Cheers,

    Ben

    Tuesday, October 16, 2018 12:27 AM
  • When it will be available mcr.microsoft.com/windows/servercore:ltsc2019 or 1809 TAG

    ?

    I am receiving error

    Error response from daemon: manifest for mcr.microsoft.com/windows/servercore:1809 not found

    Wednesday, October 17, 2018 11:48 AM
  • I think they might hold off until it goes GA to the rest of the world. Currently (as far as I'm aware) it's only available to certain groups. The wider world out there haven't received the updates yet/can't download yet.

    Wednesday, October 17, 2018 2:37 PM
  • As others have said, the images have been pulled:

    However, I discovered an alternative source for the ltsc2019/1809 images when looking through old TechNet videos and using tags based on build-numbers.  (The GA of 1809 was build 10.0.17763, and is still up at the time of this posting.)

    docker pull mcr.microsoft.com/os/windowsservercore/insider:10.0.17763.1
    docker tag mcr.microsoft.com/os/windowsservercore/insider:10.0.17763.1 microsoft/windowsservercore:latest
    docker pull mcr.microsoft.com/os/nanoserver/insider:10.0.17763.1
    docker tag mcr.microsoft.com/os/nanoserver/insider:10.0.17763.1 microsoft/nanoserver:latest

    (Also at the time of this posting 'latest' tags are pointing to these versions)

    If you've updated the Server 2019 last week, the build version will be 10.0.17763.55, but the minor version ticks still allow the images to run with process isolation.

    Having said that, there's probably a reason that the images were pulled, and these ones may have just fallen through the cracks.  I did receive a blue-screen related to NTFS once in the past 5 days, but didn't notice anything missing.

    I would suggest that anyone running the image should assume that it will delete all of your files, open you up to exploits, and allow Cortana to take over your consciousness.

    • Proposed as answer by distaula Wednesday, October 17, 2018 5:24 PM
    Wednesday, October 17, 2018 5:20 PM
  • @distaula

    That issue is still under investigation. Please don't try to scare the rest of us here.

    Please check the statement here.

    https://www.microsoft.com/en-us/cloud-platform/windows-server-trial


    Sic Parvis Magna

    Thursday, October 18, 2018 12:56 AM
  • I wasn't attempting to scare, I was providing an alternate link to the 1809 base image that I had discovered, but I also wanted to remind people that Microsoft had removed this build from all official sources for a reason, so if someone chooses to use it, they should do so with caution.
    Thursday, October 18, 2018 4:25 PM
  • No one is scaring anyone. This issue was resolved on the 9th of October already and Windows 10 1809, Windows Server 2019 and Windows Server 1809 was made available again with the fix for KFR in place.

    If you click through on the link you provided, you'll see John Cable's blog indicating this.

    All we are looking for are the docker images that were also removed. But since all versions are available again, we're merely wondering why the docker images aren't also available.

    Friday, October 19, 2018 2:30 PM
  • Hey guys,

    Does anyone know when the images will be re-released?

    Cheers,

    Ben

    Tuesday, October 23, 2018 12:33 AM
  • Greetings,

    Sorry, I have no idea about the re-release date.

    We may have to monitor their blogs at the moment.

    https://cloudblogs.microsoft.com/windowsserver/


    Sic Parvis Magna


    Tuesday, October 23, 2018 1:05 AM
  • Goto search and find your windows version. like in windows 10 you can run 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)



    • Edited by sjai_7147 Friday, June 21, 2019 6:27 AM more explanation
    Friday, June 21, 2019 6:13 AM