Allow pulling uplevel container images on an RS5 host.

[veerun14]

Description
Allow pulling uplevel container images on an RS5 host. Running uplevel container images on an RS5 host via hyperv isolation should be supported

Steps to reproduce the issue:

1. Ensure that your windows build 17763 with all the update packages installed
2. docker pull mcr.microsoft.com/windows/servercore:1903

Describe the results you received:
This is what docker daemon log produces:

time="2019-05-23T09:14:23.753050000-07:00" level=debug msg="mcr.microsoft.com/windows/servercore:1903 resolved to a manifestList object with 1 entries; looking for a unknown/amd64 match" time="2019-05-23T09:14:23.755049700-07:00" level=debug msg="will prefer Windows entries with version 10.0.17763" time="2019-05-23T09:14:23.756050200-07:00" level=debug msg="a Windows version 10.0.18362-based image is incompatible with a 10.0.17763 host

Windows version 10.0.18362-based image is incompatible with a 10.0.17763 host

Describe the results you expected:
Should be able to pull the container image.

Additional information you deem important (e.g. issue happens only occasionally):
Issue happens all the time.

Output of docker version:

Client:
 Version:           master-dockerproject-2019-05-22
 API version:       1.40
 Go version:        go1.12.5
 Git commit:        57aa7731
 Built:             Wed May 22 23:47:38 2019
 OS/Arch:           windows/amd64
 Experimental:      false

Server:
 Engine:
  Version:          master-dockerproject-2019-05-22
  API version:      1.41 (minimum version 1.24)
  Go version:       go1.12.5
  Git commit:       0805242
  Built:            Wed May 22 23:58:19 2019
  OS/Arch:          windows/amd64
  Experimental:     true

Output of docker info:

Client:
 Debug Mode: false

Server:
 Containers: 4
  Running: 0
  Paused: 0
  Stopped: 4
 Images: 2
 Server Version: master-dockerproject-2019-05-22
 Storage Driver: windowsfilter (windows) lcow (linux)
  Windows:
  LCOW:
 Logging Driver: json-file
 Plugins:
  Volume: local
  Network: ics l2bridge l2tunnel nat null overlay transparent
  Log: awslogs etwlogs fluentd gcplogs gelf json-file local logentries splunk syslog
 Swarm: inactive
 Default Isolation: process
 Kernel Version: 10.0 17763 (17763.1.amd64fre.rs5_release.180914-1434)
 Operating System: Windows Server 2019 Datacenter Version 1809 (OS Build 17763.529)
 OSType: windows
 Architecture: x86_64
 CPUs: 56
 Total Memory: 286.7GiB
 Name: TK5-3WP16R0705
 ID: 9ee90bd6-9e11-4236-a572-176d9055e2b8
 Docker Root Dir: C:\ProgramData\docker
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: true
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
Physical

[lowenna]

@veerun14 The fix is really simple. But I won't submit it until the backport fix to allow n+1 to run on RS5 as xenon is available. The branch is https://github.com/microsoft/docker/tree/jjh/39328, the change is microsoft@59d1597

[lowenna]

New experience (this is on RS5)

PS C:\vol> docker pull mcr.microsoft.com/windows/nanoserver:1903
1903: Pulling from windows/nanoserver
b1cdaa8beba7: Pull complete
Digest: sha256:ba24e09384e9eac1962f558ba36900defea9a4bd4bc5a9bcb2dea1f78e7561f7
Status: Downloaded newer image for mcr.microsoft.com/windows/nanoserver:1903
mcr.microsoft.com/windows/nanoserver:1903
PS C:\vol> docker run --rm mcr.microsoft.com/windows/nanoserver:1903 cmd /c echo hello
c:\binaries\docker.exe: Error response from daemon: hcsshim::CreateComputeSystem 0cf5ad0ec9c4cfba00ed54cbaefcbf6136504ec92400f9fd1234f945c30f0620: The container operating system does not match the host operating system.
(extra info: {"SystemType":"Container","Name":"0cf5ad0ec9c4cfba00ed54cbaefcbf6136504ec92400f9fd1234f945c30f0620","Owner":"docker","VolumePath":"\\\\?\\Volume{35f66cac-4080-4040-8506-b4b9f4602896}","IgnoreFlushesDuringBoot":true,"LayerFolderPath":"C:\\control\\windowsfilter\\0cf5ad0ec9c4cfba00ed54cbaefcbf6136504ec92400f9fd1234f945c30f0620","Layers":[{"ID":"8ee10065-8fbd-5849-80a2-f70df6417eff","Path":"C:\\control\\windowsfilter\\b311cf56debbaf0830d567553a81425e4302042fe604ca5bdf7702f4b9141630"}],"HostName":"0cf5ad0ec9c4","HvPartition":false,"EndpointList":["CAEF04BB-0E43-4830-A291-9D51DAA37D61"],"AllowUnqualifiedDNSQuery":true}).
PS C:\vol> docker run --rm --isolation=hyperv mcr.microsoft.com/windows/nanoserver:1903 cmd /c echo hello
c:\binaries\docker.exe: Error response from daemon: container e9471676d65d2d2e0da8b1ec02fc85afcdc920a82febeb355d454ebcd0b02aad encountered an error during Start: failure in a Windows system call: The virtual machine or container exited unexpectedly. (0xc0370106).