Answers: <p>seems support ended for above mentioned image its no longer in their registry maybe </p>
  
  <p><a href="https://devblogs.microsoft.com/dotnet/net-core-container-images-now-published-to-microsoft-container-registry/" rel="nofollow noreferrer">https://devblogs.microsoft.com/dotnet/net-core-container-images-now-published-to-microsoft-container-registry/</a></p>
  
Answers: CC BY-SA 4.0
Answers: 2019-12-03T16:30:37.477Z
Answers: While they stopped using the docker CR, the docker pages for the images list the correct link to mcr.microsoft.com
Answers: Dawnkeeper
Answers: CC BY-SA 4.0
Answers: 2019-12-03T11:43:36.150Z
Answers: 2019-12-03T11:43:36.150Z
Answers: ankit
Answers: <p>The problem is twofold:</p>
  
  <ul>
  <li><p>The Win10 LTSB is on its newest version and Docker has stopped supporting this version.<br>
  This stops Docker from updating.</p></li>
  <li><p>Microsoft has moved to its own container registry and in doing so abandoned support for older Docker versions. So while I was pulling from the right registry it could not find a fitting image.</p></li>
  </ul>
  
  <p><strong>Solution:</strong> get an up-to-date, non-LTSB version of Windows</p>
  
  <p>Additional Info:<br>
  While the error message did not help in finding the cause the docker log did:</p>
  
  <pre><code>[WindowsDaemon  ][Info   ] debug: a Windows version 10.0.18363-based image is incompatible with a 10.0.14393 host
  </code></pre>
  
Answers: CC BY-SA 4.0
Answers: 2019-12-03T16:27:32.727Z
Answers: 2019-12-03T16:27:32.727Z
Answers: Dawnkeeper
Body: <p>I tried pulling the windows/nanoserver image.<br>
  After that failed I looked around and found <a href="https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-base-images" rel="nofollow noreferrer">this site</a><br>
  Every one of them fails with the same error message</p>
  
  <pre><code>#docker pull mcr.microsoft.com/windows/nanoserver:1909
  ltsc2019: Pulling from windows/servercore
  no matching manifest for unknown in the manifest list entries
  </code></pre>
  
  <p>Additional Info:<br>
  Docker version: 18.09.2, build 6247962<br>
  Win10 Enterprise 2016 LTSB: Version 10.0.14393 Build 14393</p>
  
Tags: <docker><windows>
Title: Pulling windows base images fails
UserDisplayName: Dawnkeeper
ThreadText: # Pulling windows base images fails
  
  (Asked by: username_0 on 2019-12-02)
  
  I tried pulling the windows/nanoserver image.  
  After that failed I looked around and found [this site](https://docs.microsoft.com/en-us/virtualization/windowscontainers/manage-containers/container-base-images)  
  Every one of them fails with the same error message
  
  ```
  #docker pull mcr.microsoft.com/windows/nanoserver:1909
  ltsc2019: Pulling from windows/servercore
  no matching manifest for unknown in the manifest list entries
  
  ```
  
  Additional Info:  
  Docker version: 18.09.2, build 6247962  
  Win10 Enterprise 2016 LTSB: Version 10.0.14393 Build 14393
  
  **Tags:** docker, windows
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_0 on 2019-12-03. Score: 3 | Accepted answer
  
  The problem is twofold:
  
  * The Win10 LTSB is on its newest version and Docker has stopped supporting this version.  
    This stops Docker from updating.
  * Microsoft has moved to its own container registry and in doing so abandoned support for older Docker versions. So while I was pulling from the right registry it could not find a fitting image.
  
  **Solution:** get an up-to-date, non-LTSB version of Windows
  
  Additional Info:  
  While the error message did not help in finding the cause the docker log did:
  
  ```
  [WindowsDaemon  ][Info   ] debug: a Windows version 10.0.18363-based image is incompatible with a 10.0.14393 host
  
  ```
  
  
  ---
  
  ### Answer by username_1 on 2019-12-03. Score: 0
  
  seems support ended for above mentioned image its no longer in their registry maybe
  
  <https://devblogs.microsoft.com/dotnet/net-core-container-images-now-published-to-microsoft-container-registry/>
  
  > **Comments:**
  > **username_0**: While they stopped using the docker CR, the docker pages for the images list the correct link to mcr.microsoft.com  
  
  ---
  
  