Windows w/ Linux Container - "The request is not supported"

I have two Windows 2019 servers, one that is able to run Linux containers without any issues, and the other that can’t. They are running identical versions of docker (18.09). I have tried rebuilding the server that can’t run the Linux containers from scratch numerous times. CreateComputeSystem — The request is not supported. Why is this happening!!!

Both servers have the exact same Linuxkit LCOW kernel and initrd.img files (https://github.com/linuxkit/lcow/releases/tag/v4.14.35-v0.3.9) in C:\Program Files\Linux Containers.

Here is the docker info, version, and what happens when I try to run an Ubuntu image on each of them:

Non-Working Server-----

PS C:\Windows\system32> docker version
Client:
Version: 18.09.1
API version: 1.39
Go version: go1.10.6
Git commit: 20b67756d0
Built: unknown-buildtime
OS/Arch: windows/amd64
Experimental: false

Server:
Engine:
Version: 18.09.1
API version: 1.39 (minimum version 1.24)
Go version: go1.10.6
Git commit: 20b67756d0
Built: 01/09/2019 17:09:57
OS/Arch: windows/amd64
Experimental: true
PS C:\Windows\system32> docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 18.09.1
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 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 Standard Version 1809 (OS Build 17763.253)
OSType: windows
Architecture: x86_64
CPUs: 2
Total Memory: 7.999GiB
Name: CED-TX-CNT-REPO
ID: J2Q6:XKKG:P3Z6:HXQ2:X6Y5:AB6D:RKQ2:5POT:ER27:YWV6:CC7X:5FM5
Docker Root Dir: D:\DockerData
Debug Mode (client): false
Debug Mode (server): false
Registry: /index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

PS C:\Windows\system32> docker run -it ubuntu
C:\Program Files\Docker\docker.exe: Error response from daemon: failed to start service utility VM (createreadwrite): CreateComputeSystem 193d1f4e0598d23378352251eb6ab44f3b33937c58e7406b9effa8ec6e213e8e_svm: The request is not supported.
(extra info: {“SystemType”:“container”,“Name”:“193d1f4e0598d23378352251eb6ab44f3b33937c58e7406b9effa8ec6e213e8e_svm”,“Layers”:null,“HvPartition”:true,“HvRuntime”:{“ImagePath”:“C:\Program Files\Linux Containers”,“LinuxInitrdFile”:“initrd.img”,“LinuxKernelFile”:“kernel”},“ContainerType”:“linux”,“TerminateOnLastHandleClosed”:true}).
See ‘C:\Program Files\Docker\docker.exe run --help’.
PS C:\Windows\system32>

Working Server------

PS C:\Windows\system32> docker version
Client:
Version: 18.09.1
API version: 1.39
Go version: go1.10.6
Git commit: 20b67756d0
Built: unknown-buildtime
OS/Arch: windows/amd64
Experimental: false

Server:
Engine:
Version: 18.09.1
API version: 1.39 (minimum version 1.24)
Go version: go1.10.6
Git commit: 20b67756d0
Built: 01/09/2019 17:09:57
OS/Arch: windows/amd64
Experimental: true
PS C:\Windows\system32> docker info
Containers: 1
Running: 0
Paused: 0
Stopped: 1
Images: 3
Server Version: 18.09.1
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 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 Standard Version 1809 (OS Build 17763.253)
OSType: windows
Architecture: x86_64
CPUs: 2
Total Memory: 7.999GiB
Name: CED-TX-TFS-BLD4
ID: LCTD:67G6:XROP:G4AR:ECKY:LNKU:5QLY:BO5A:CEB5:PNMS:4UJ2:4HNO
Docker Root Dir: D:\DockerData
Debug Mode (client): false
Debug Mode (server): false
Registry: /index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

PS C:\Windows\system32> docker run -it ubuntu
root@140c98da734e:/#

I currently have the same issue as you but on a custom made “docker” system (compiled my own dockerd and docker client).

I am starting to wonder whether I pulled some new code related to HCS which is not supported yet in my Windows build (Windows Pro version 1809)…

My problem turned out to be that I needed to do Install-WindowsFeature Containers,Hyper-V before docker.

Thanks a lot, had the same issue.
I activated Hyper-V feature but not the Containers one!