Getting "The request is not supported" while trying to execute docker run

[maksim36ua]

Hi! I'm using Windows Server 2019 (1809, build 17763), with "Containers" feature enabled. Performed all the steps from README.md. When trying to execute

docker run --platform linux --rm -ti busybox sh

I get following error message:

Error response from daemon: failed to start service utility VM (createreadwrite): CreateComputeSystem 123aa681adc9fe7814322a95068e28911b4f42d887cd734fe3b3a02dc3b90203_svm: The request is not supported. (extra info: {"SystemType":"container", "Name":"123aa681adc9fe7814322a95068e28911b4f42d887cd734fe3b3a02dc3b90203_svm", "Layers":null, "HvPartition":true, "HvRuntime":{"ImagePath":"C:\\Program Files\\Linux Containers", "LinuxInitrdFile":"initrd.img", "LinuxKernelFile":"kernel"}, "ContainerType":"linux", "TerminateOnLastHandleClosed":true}).

docker version
Client:
Version: 18.09.2
API version: 1.39
Go version: go1.10.6
Git commit: 1ac774dfdd
Built: unknown-buildtime
OS/Arch: windows/amd64
Experimental: false

Server:
Engine:
Version: 18.09.2
API version: 1.39 (minimum version 1.24)
Go version: go1.10.6
Git commit: 1ac774dfdd
Built: 02/10/2019 04:13:25
OS/Arch: windows/amd64
Experimental: true

docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 6
Server Version: 18.09.2
Storage Driver: windowsfilter (windows) lcow (linux)
Windows:
LCOW:
Logging Driver: json-file
Plugins:
Volume: local
Network: ics l2bridge l2tunnel nat null overlay transparent
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.316)
OSType: windows
Architecture: x86_64
CPUs: 2
Total Memory: 15.71GiB
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: true
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

Might be not related to LCOW, but still not sure, where shall I ask for help with this issue. Will appreciate any suggestions regarding possible root causes

[Vacant0mens]

This error comes from the image you're referencing not being compatible with the current OS you're running.

Since busybox is a linux image, you'll have to specify --isolation=hyperv in your run command. But I'm not sure this is fully supported yet.

I'm also fairly certain that Server 2019 is not officially supported with Docker EE engine, but you might try updating to 18.09.7 just to see, or try version 19.03.0-rc2 if you're feeling brave (but they're having some issues with the hash on the package file last I checked.)

[Vacant0mens]

Correction:

It may be related to the way that you're phrasing your run command. I discovered this the hard way.

For example:

docker run -d -p 9000:9000 --name portainer --restart always -v \\.\pipe\docker_engine:\\.\pipe\docker_engine -v E:\Portainer:C:\data portainer/portainer:windows1809-amd64

works. ... But

docker run -d --restart=always --mount type=npipe,source=\\.\pipe\docker_engine,destination=\\.\pipe\docker_engine --mount type=bind,source=E:\Portainer,destination=C:\data -p 9000:9000 --name portainer portainer/portainer:windows1809-amd64

throws the The request is not supported error.

I would try using different parameters or alternative parameters to what you have and see if changing something gives you the same errors.

[alatas]

I had the same issue on a clean win2019(1809) + docker(v19.03.2) + lcow (v4.14.34)
I enabled the hyper-v feature from server configuration manager, and restarted the server. the issue was solved.