Docker failed to start service utility VM with LCOW on windows server 2019

[red00dragon]

I try to run a Docker container on a fresh windows 2019 machine but on pulling it I get following error message after a night long waiting:

C:\Program Files\Docker\docker.exe: failed to register layer: failed to start service utility VM (applydiff d3d444b7e4622ad1fed86aca20a57e5fec56d756feced70ef51bfeb0eb85aee5): container d3d444b7e4622ad1fed86aca20a57e5fec56d756feced70ef51bfeb0eb85aee5_svm encountered an error during CreateContainer: failure in a Windows system call: A connection could not be established with the container or virtual machine. (0xc0370108) extra info: {"SystemType":"container","Name":"d3d444b7e4622ad1fed86aca20a57e5fec56d756feced70ef51bfeb0eb85aee5_svm","Layers":null,"HvPartition":true,"HvRuntime":{"ImagePath":"C:\\Program Files\\Linux Containers","LinuxInitrdFile":"initrd.img","LinuxKernelFile":"bootx64.efi"},"ContainerType":"linux","TerminateOnLastHandleClosed":true}.
See 'C:\Program Files\Docker\docker.exe run --help'.

The windows runs under VMWare(V6.7 U3) where virtualization is enabled.
I tried the same thing with a virtual machine from azure which was working great. Can it be a problem with VMWare(V6.7 U3)? Do we need to activate the something more then the hardware virtualization flag?

I used following commands:

1. Install-WindowsFeature -Name Hyper-V -IncludeManagementTools -Restart 
A Reboot will happen 
2. Install-Module DockerProvider 
3. Install-Package Docker -ProviderName DockerProvider -RequiredVersion preview 
Reboot your machine manual once again. 
4. [Environment]::SetEnvironmentVariable("LCOW_SUPPORTED", "1", "Machine") 
5. Restart-Service docker 6. docker run --name am-redis -p 6379:6379 --memory="4g" -d redis redis-server --appendonly yes

docker info:

Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 17.10.0-ee-preview-3
Storage Driver: windowsfilter (windows) lcow (linux)
 LCOW:
Logging Driver: json-file
Plugins:
 Volume: local
 Network: ics l2bridge l2tunnel nat null overlay transparent
 Log: awslogs etwlogs fluentd json-file 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
OSType: windows
Architecture: x86_64
CPUs: 2
Total Memory: 16GiB
Name: SV000034
ID: SBES:OFCG:TVZH:LO3Z:FPYQ:CQ3G:OEOP:JAYB:TGZA:VW35:SIYE:S7BK
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

docker version:

Client:
 Version:      17.10.0-ee-preview-3
 API version:  1.33
 Go version:   go1.8.4
 Git commit:   1649af8
 Built:        Fri Oct  6 17:52:28 2017
 OS/Arch:      windows/amd64

Server:
 Version:      17.10.0-ee-preview-3
 API version:  1.34 (minimum version 1.24)
 Go version:   go1.8.4
 Git commit:   b8571fd
 Built:        Fri Oct  6 18:01:48 2017
 OS/Arch:      windows/amd64
 Experimental: true

[philipp-ch]

Did you find a solution? I have the exact same setup and problem with linux containers. BR

[umair13adil]

I am facing a similar issue:

Service 'storage-temp' failed to build: failed to start service utility VM (createreadwrite): kernel 'C:\Program Files\Linux 
Containers\kernel' not found

Running docker version:

Client: Docker Engine - Enterprise
Version: 19.03.5
API version: 1.40
Go version: go1.12.12
Git commit: 2ee0c57608
Built: 11/13/2019 08:00:16
OS/Arch: windows/amd64
Experimental: false

Server: Docker Engine - Enterprise
Engine:
Version: 19.03.5
API version: 1.40 (minimum version 1.24)
Go version: go1.12.12
Git commit: 2ee0c57608
Built: 11/13/2019 07:58:51
OS/Arch: windows/amd64
Experimental: true

[umair13adil]

This issue was resolved for me when I followed the steps mentioned in this answer on StackOverflow.

[maxisam]

I have exact setup as you do.
My case was caused by carbon black. It works after adjusting the policy.

[claytoncalixto]

I have this same problem:

docker: Error response from daemon: failed to start service utility VM (createreadwrite): hcsshim::CreateComputeSystem 4c2529611fb4bbb71498a5466d36cc3fe8a4a84ab3f70e46bdaeee9ee99eebb8_svm: Não há suporte para o pedido.
(extra info: {"SystemType":"container","Name":"4c2529611fb4bbb71498a5466d36cc3fe8a4a84ab3f70e46bdaeee9ee99eebb8_svm","Layers":null,"HvPartition":true,"HvRuntime":{"ImagePath":"C:\Program Files\Linux Containers","LinuxInitrdFile":"initrd.img","LinuxKernelFile":"kernel"},"ContainerType":"linux","TerminateOnLastHandleClosed":true}).

Someone managed to solve it?

[imaginois]

I have the same problem. Still no resolve

I have this same problem:

docker: Error response from daemon: failed to start service utility VM (createreadwrite): hcsshim::CreateComputeSystem 4c2529611fb4bbb71498a5466d36cc3fe8a4a84ab3f70e46bdaeee9ee99eebb8_svm: Não há suporte para o pedido.
(extra info: {"SystemType":"container","Name":"4c2529611fb4bbb71498a5466d36cc3fe8a4a84ab3f70e46bdaeee9ee99eebb8_svm","Layers":null,"HvPartition":true,"HvRuntime":{"ImagePath":"C:\Program Files\Linux Containers","LinuxInitrdFile":"initrd.img","LinuxKernelFile":"kernel"},"ContainerType":"linux","TerminateOnLastHandleClosed":true}).

Someone managed to solve it?

[davidberglund]

I have the same issue. Is there a solution for this, please? If there's a guide somewhere to getting started with LCOW, I'd like to see it.

docker run --platform=linux ubuntu
C:\Program Files\Docker\docker.exe: Error response from daemon: failed to start service utility VM (createreadwrite): hcsshim::CreateComputeSystem 6327851bf6d9adac9b3eeb402100b73d0666dbabe1fabf041bd7d59213fd88d2_svm: The request is not supported.
(extra info: {"SystemType":"container","Name":"6327851bf6d9adac9b3eeb402100b73d0666dbabe1fabf041bd7d59213fd88d2_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'.

[saritapandey19]

This issue was resolved for me when I followed the steps mentioned in this answer on StackOverflow.

I also followed the same steps mention in above link and the issue got resolved. Thank you .

[darrens280]

The solution for me was due to the fact the (Azure) VM Scale Set instance that I was attempting to run the Docker commands from (Standard B2_ms), does not support Nested Virtualization, and therefore the Docker service would not start. Once I modified the VM SKU to Standard_D2_v5 then the Docker service would start successfully, and I could successfully PULL an image. See Azure docs for which VM SKUs support Nested Virtualization: https://learn.microsoft.com/en-us/azure/virtual-machines/dv5-dsv5-series