Ws2019containers (#370)

* Adjust table

* Add pull instructions refering to MCR

* Update deploy-containers-on-server.md

virtualization/windowscontainers/deploy-containers/deploy-containers-on-server.md

@@ -71,6 +71,24 @@ Install-Package -Name docker -ProviderName DockerMsftProvider -Update -Force -Re
 
 Before working with Windows Containers, a base image needs to be installed. Base images are available with either Windows Server Core or Nano Server as the container operating system. For detailed information on Docker container images, see [Build your own images on docker.com](https://docs.docker.com/engine/tutorials/dockerimages/).
 
+With the release of Windows Server 2019, Microsoft-sourced container images are moving to a new registry called the Microsoft Container Registry. Container images published by Microsoft should continue to be discovered via Docker Hub. For new container images published with Windows Server 2019 and beyond, you should look to pull them from the MCR. For older container images published before Windows Server 2019, you should continue to pull them from Docker's registry.
+
+### Windows Server 2019 and newer
+
+To install the 'Windows Server Core' base image run the following:
+
+```PowerShell
+docker pull mcr.microsoft.com/windows/servercore:ltsc2019
+```
+
+To install the 'Nano Server' base image run the following:
+
+```PowerShell
+docker pull mcr.microsoft.com/windows/nanoserver:1809
+```
+
+### Windows Server 2016 (versions 1607-1803)
+
 To install the Windows Server Core base image run the following:
 
 ```PowerShell

virtualization/windowscontainers/deploy-containers/system-requirements.md

@@ -15,7 +15,7 @@ This guides list the requirements for a Windows container Host.
 
 ## OS Requirements
 
-- The Windows container feature is only available on Windows Server build 1709, Windows Server 2016 (Core and with Desktop Experience) and Windows 10 Professional and Enterprise (Anniversary Edition).
+- The Windows container feature is only available on Windows Server 2016 (Core and with Desktop Experience), Windows 10 Professional and Enterprise (Anniversary Edition) and later.
 - The Hyper-V role must be installed before running Hyper-V Containers
 - Windows Server Container hosts must have Windows installed to c:\. This restriction does not apply if only Hyper-V Containers will be deployed.
 
@@ -24,7 +24,7 @@ This guides list the requirements for a Windows container Host.
 If a Windows container host will be run from a Hyper-V virtual machine, and will also be hosting Hyper-V Containers, nested virtualization will need to be enabled. Nested virtualization has the following requirements:
 
 - At least 4 GB RAM available for the virtualized Hyper-V host.
-- Windows Server build 1709, Windows Server 2016, or Windows 10 on the host system, and Windows Server (Full, Core) in the virtual machine.
+- Windows Server 2019, Windows Server version 1803, Windows Server version 1709, Windows Server 2016, or Windows 10 on the host system, and Windows Server (Full, Core) in the virtual machine.
 - A processor with Intel VT-x (this feature is currently only available for Intel processors).
 - The container host VM will also need at least 2 virtual processors.
 
@@ -42,7 +42,7 @@ Windows Containers are offered with two container base images, Windows Server Co
 </thead>
 <tbody>
 <tr valign="top">
-<td><center>Windows Server 2016 (Standard or Datacenter)</center></td>
+<td><center>Windows Server 2016 / 2019 (Standard or Datacenter)</center></td>
 <td><center>Server Core / Nano Server</center></td>
 <td><center>Server Core / Nano Server</center></td>
 </tr>

virtualization/windowscontainers/deploy-containers/version-compatibility.md

@@ -26,6 +26,8 @@ As we've been improving the Windows container features, we've had to make some c
         <td style="background-color:#F1F8E9"><b>Windows 10 Fall Creators Update</b><br/>Builds 16299.*</td>
         <td style="background-color:#F1F8E9"><b>Windows Server version 1803</b><br/>Builds 17134.*</td>
         <td style="background-color:#F1F8E9"><b>Windows 10 version 1803</b><br/>Builds 17134.*</td>
+        <td style="background-color:#F1F8E9"><b>Windows Server 2019</b><br/>Builds 17763.*</td>
+        <td style="background-color:#F1F8E9"><b>Windows 10 version 1809</b><br/>Builds 17763.*</td>
     </tr>
     <tr>
         <td style="background-color:#E3F2FD"><b>Windows Server 2016</b><br/>Builds: 14393.*</td>
@@ -35,6 +37,8 @@ As we've been improving the Windows container features, we've had to make some c
         <td>Supports<br/> Only `hyperv` isolation</td>
         <td>Supports<br/> Only `hyperv` isolation</td>
         <td>Supports<br/> Only `hyperv` isolation</td>
+        <td>Supports<br/> Only `hyperv` isolation</td>
+        <td>Supports<br/> Only `hyperv` isolation</td>
     </tr>
     <tr>
         <td style="background-color:#E3F2FD"><b>Windows Server version 1709</b><br/>Builds 16299.*</td>
@@ -44,6 +48,8 @@ As we've been improving the Windows container features, we've had to make some c
         <td>Supports<br/> Only `hyperv` isolation</td>
         <td>Supports<br/> Only `hyperv` isolation</td>
         <td>Supports<br/> Only `hyperv` isolation</td>
+        <td>Supports<br/> Only `hyperv` isolation</td>
+        <td>Supports<br/> Only `hyperv` isolation</td>
     </tr>
     <tr>
         <td style="background-color:#E3F2FD"><b>Windows Server version 1803</b><br/>Builds 17134.*</td>
@@ -53,6 +59,19 @@ As we've been improving the Windows container features, we've had to make some c
         <td>Not supported</td>
         <td>Supports<br/> `process` or `hyperv` isolation</td>
         <td>Supports<br/> Only `hyperv` isolation</td>
+        <td>Supports<br/> Only `hyperv` isolation</td>
+        <td>Supports<br/> Only `hyperv` isolation</td>
+    </tr>
+    <tr>
+        <td style="background-color:#E3F2FD"><b>Windows Server 2019</b><br/>Builds 17763.*</td>
+        <td>Not supported</td>
+        <td>Not supported</td>
+        <td>Not supported</td>
+        <td>Not supported</td>
+        <td>Not supported</td>
+        <td>Not supported</td>
+        <td>Supports<br/> `process` or `hyperv` isolation</td>
+        <td>Supports<br/> Only `hyperv` isolation</td>
     </tr>
 </table>