Docker error response from daemon unsupported os linux

Troubleshooting installation on Windows

Issues with loading Memgraph​

Error during connect:
This error may indicate that the docker daemon is not running. ​

Run the Docker Desktop application and wait for it to load fully.

Error response from daemon:
open \.pipedocker_engine_linux: The system cannot find the file specified. ​

Reload the Docker Desktop application and wait for it to load fully.

Unsupported os linux​

You need to download the Windows Subsystem for Linux, and enable experimental features in Docker Desktop, under Settings -> Docker Engine, change experimental to true.

Issues when connecting to Memgraph​

While this command will start a Memgraph instance, not publishing the port will cause problems when trying to connect to the database via Memgraph Lab or mgconsole. To avoid this, you should publish the container’s port to the host using the -p flag and by specifying the port:

Issues with connecting mgconsole to the database​

Although unlikely, sometimes there are issues with connecting mgconsole to the Docker Container’s IP address because it is running on a custom IP rather than localhost . This problem is most often accompanied with the following error:

To fix this issue, just replace HOST from the first command with host.docker.internal . To find out more about networking in Docker, take a look at Networking features in Docker Desktop for Windows guide.

Find the IP address of a Docker Container​

Although unlikely, some users might experience minor difficulties after the Docker installation. Instead of running on localhost , a Docker container for Memgraph may be running on a custom IP address. Fortunately, that IP address can be found as follows:

1. Determine the ID of the Memgraph Container by issuing the command docker ps . The user should get an output similar to the following:

At this point, it is important to remember the container ID of the Memgraph Image. In our case, that is 9397623cd87e .

2. Use the this ID to retrieve the IP address of the Container:

The command above will yield the IP address that should be used when connecting to Memgraph via Memgraph Lab or mgconsole as described in the querying section. Just replace HOST from the following command with the appropriate IP address:

Accessing files from your Windows system​

Usually, you can find the Windows users directories in this location:

Unable to install the Memgraph package with dpkg ​

While running the following dpkg command:

you may encounter errors that resemble the following:

These errors indicate that you don’t have all of the necessary dependencies installed. To install the missing dependencies and finish the installation, issue the following command:

Multiple notes when starting Memgraph​

When you start a Memgraph instance, you may see the following list of notes in your terminal:

If you wish to work with built-in NetworkX modules in Memgraph, you need to install the following Python libraries:

For more information on how to install Python libraries in WSL, follow the Python installation guide. If you are not interested in working with query modules that depend on these libraries, you can ignore the warnings.

Источник

LCOW: Linux Containers on Windows Server

Published by Felipe Crochik on February 16, 2019 February 16, 2019

Recent Posts

Archives

Note: LCOW support is currently experimental and under active development.

Before anything else, it is not yet ready for prime time or work out of the box…

Now that it is out of the way, let’s continue:

Requirements

• Windows Server 1709 – Build 16299+
• Hyper-V support, if running on Virtual Machine “Nested Virtualization” must be supported and enabled.

On azure, this means that you MUST use a Dv3 or Ev3 instance (this may be the most important detail you will find here 🙂 )

HowTo

Create Virtual Machine

In the case of Azure, make sure to select an instance size of the latest version (e.g. D2sV3) and Windows Server 2019.

Install Docker EE

Connect to the virtual machine using RDP and on the “DOS prompt” start powershell:

Install Docker EE using DockerMsftProvider:

You may be prompted to install the NuGet Provider:

Enabled Windows “Containers” Feature

Most likely you will get the result above indicating that you need to Restart (e.g. Restart = yes). In this case, restart the virtual machine:

Reconnect to the Virtual machine using RDP and switch to powershell.

At this point, you should be able to start the docker daemon and even run a windows container on it.

Enable Experimental features

Start the docker service to check:

Create the directory C:Program FilesLinux Containers:

Delete the release.zip file after that:

Make sure Hyper-V feature is installed

You may get disconnected from the virtual machine if a restart is needed. Wait a few seconds and reconnect.

Fun time:

Troubleshooting

Missing Hyper-V

Use a different virtual machine with hardware support for Hyper-V Nested virtualization. In the Azure case, make sure to use a Dv3 or Ev3 instance.

Missing Hyper-V. Install Hyper-V Windows feature (instructions above).

OS Build not supported

Most likely the Windows Server version doesn’t support LCOW. Check it by running:

The first build to include support was 16299.

Containers Feature not installed

You need to install docker and the Containers Windows Feature (see previous instructions on how).

Missing platform parameter

Assuming that you have followed all the instructions and everything else is OK, this should simply indicate that you are missing the –platform=linux parameter.

Try again adding –platform=linux after the run:

Experimental Features disabled

If after including the platform argument you get the result above you haven’t enabled the docker experimental features.

Missing LCOW (linuxkit)

Follow instructions above to download the linuxKit.

References

james · April 29, 2019 at 2:46 am

how to run linux containers in AWS windows server 2019 base datacenter edition as i have followed this blog to run LCOW in AWS windows server 2019 and was through “Error response from daemon: failed to start service utility VM (createreadwrite): CreateComputeSystem 500857995b75ae7b7cb918dd32fc032f7a851004d31d60ee1b544e12b34bfc9b_svm: The virtual machine could not be started because a required feature is not installed.” Any suggestions. Thanks

Felipe Crochik · May 1, 2019 at 6:17 am

Hi James. I haven’t tried this on AWS. Have you checked that nested virtualization is supported on the instance you created?

SGP · December 13, 2019 at 6:44 pm

I am currently facing the same issue described by James while using Windows Server 2019 on AWS.
I was expecting this to work just fine with a recent Hyper-V AMI (AMI ID: ami-0127ee9a754557b67 – Windows_Server-2019-English-Full-HyperV-2019.11.13), but when attempting to run a Linux Docker image I am getting the same error.

C:UsersAdministrator>docker run -ti –isolation=hyperv 84120c6c3491
docker: Error response from daemon: failed to start service utility VM (createreadwrite): hcsshim::CreateComputeSystem c5185a5d19859af629d4b383a1c53b3e173748ca102430c47edcf9f11cb926c1_svm: The virtual machine could not be started because a required feature is not installed.
(extra info: <“SystemType”:”container”,”Name”:”c5185a5d19859af629d4b383a1c53b3e173748ca102430c47edcf9f11cb926c1_svm”,”Layers”:null,”HvPartition”:true,”HvRuntime”:<“ImagePath”:”C:\Program Files\Linux Containers”,”LinuxInitrdFile”:”initrd.img”,”LinuxKernelFile”:”kernel”>,”ContainerType”:”linux”,”TerminateOnLastHandleClosed”:true>).

Any ideas would be greatly appreciated.

I have reviewed the installed Windows components, docker packages, experimental features, default platform, etc., set, re-set, rebooted, … still no joy.

SGP · December 13, 2019 at 6:47 pm

oops… my last example includes the “–issolation=hyperv” parameter on “docker run”… this was just another experiment. I copied the wrong example.

This same behavior happens without this parameter included which is my expected scenario.

Indian Velumani · December 17, 2019 at 3:21 am

I tried like and I got error like this.
In Windows 2016 server std.

C:Program FilesDockerdocker.exe: failed to register layer: failed to start service utility VM (applydiff e8e51d13ddc7
93adab0dad0972c8ccba89df623886232a4df37553c5a10248c0): container e8e51d13ddc793adab0dad0972c8ccba89df623886232a4df37553c
5a10248c0_svm encountered an error during CreateContainer: failure in a Windows system call: The data is invalid. (0xd)
extra info: <“SystemType”:”container”,”Name”:”e8e51d13ddc793adab0dad0972c8ccba89df623886232a4df37553c5a10248c0_svm”,”Lay
ers”:null,”HvPartition”:true,”HvRuntime”: <“ImagePath”:”C:\Program Files\Linux Containers”,”LinuxInitrdFile”:”initrd.im
g”,”LinuxKernelFile”:”bootx64.efi”>,”ContainerType”:”linux”,”TerminateOnLastHandleClosed”:true>.

Indian Velumani · December 17, 2019 at 3:26 am

I tried in windows 2016 server std edition
But I got like this, Any idea to resolve this.

C:Program FilesDockerdocker.exe: failed to register layer: failed to start service utility VM (applydiff e8e51d13ddc7
93adab0dad0972c8ccba89df623886232a4df37553c5a10248c0): container e8e51d13ddc793adab0dad0972c8ccba89df623886232a4df37553c
5a10248c0_svm encountered an error during CreateContainer: failure in a Windows system call: The data is invalid. (0xd)
extra info: <“SystemType”:”container”,”Name”:”e8e51d13ddc793adab0dad0972c8ccba89df623886232a4df37553c5a10248c0_svm”,”Lay
ers”:null,”HvPartition”:true,”HvRuntime”: <“ImagePath”:”C:\Program Files\Linux Containers”,”LinuxInitrdFile”:”initrd.im
g”,”LinuxKernelFile”:”bootx64.efi”>,”ContainerType”:”linux”,”TerminateOnLastHandleClosed”:true>.

nedumaran · April 21, 2020 at 5:58 am

Hi Velumani, i am also facing the same error that you face. Just wanted to check if you were able to fix this. if so, could you please share the solution for this error?

Источник

LCOW on Edge is not working #4004

Expected behavior

I can pull and run docker containers in windows using LCOW.

Actual behavior

I am unable to pull or run LCOW containers.

Information

• LCOW works fine in docker desktop 2.0.3.0.
• LCOW stopped working when I upgraded to 2.0.4.0 This is when Docker 19.03.0-beta3 was added.
• Windows Version: Windows 10 1803 (OS Build 17134.799)
• Docker for Windows Version: Edge 2.0.4.1 (34207)

The text was updated successfully, but these errors were encountered:

This works ok for me so far.

Ok repro’d this now.

Got confirmation: latest LCOW support requires windows 19.03, you’ll need to update windows.

I see my windows version is 19.03.1 and kernal version is 10.0 17134 but still facing the same issue. Can you please check what can be the issue at my end?

$ docker version
Client: Docker Engine — Community
Version: 19.03.1
API version: 1.40
Go version: go1.12.5
Git commit: 74b1e89
Built: Thu Jul 25 21:17:08 2019
OS/Arch: windows/amd64
Experimental: true

Server: Docker Engine — Community
Engine:
Version: 19.03.1
API version: 1.40 (minimum version 1.24)
Go version: go1.12.5
Git commit: 74b1e89
Built: Thu Jul 25 21:25:07 2019
OS/Arch: windows/amd64
Experimental: true

$ docker info
Client:
Debug Mode: false
Plugins:
app: Docker Application (Docker Inc., v0.8.0)
buildx: Build with BuildKit (Docker Inc., v0.2.2-10-g3f18b65-tp-docker)

Источник

LCOW: Invalid Platform OS «linux» #2241

Expected behavior

Build a Linux image for CentOS 6.8 while using Windows containers

Actual behavior

Unable to pull the image or build.
Returns an error saying:

Error response from daemon: invalid platform: invalid platform os «linux»

Information

• Windows Version: Windows 10 Enterprise Version 10.0.14393 Build 14393
• Docker for Windows Version: Version 18.03.0-ce-win59 (16762)

I’m working on a project that requires running both Linux containers and Windows containers at the same time. I’m not using the most recent version of Docker in this channel, because that version crashes whenever I switch to Windows containers (#1898).

Steps to reproduce the behavior

1. Start Docker for Windows
2. Switch to using Windows containers
3. Enable Experimental features in the Docker settings
4. In command line, run docker pull —platform=linux centos:6.8

The text was updated successfully, but these errors were encountered:

Downloaded 18.03.0-ce-win72 and now I just get an «unsupported os linux»

Has the experimental feature been removed?

Hi @necroTaxonomist. Yes, you have to enable experimental in the daemon settings. We disabled it because if you pull an lcow image and disable experimental, it bricks your windows daemon.

@ebriney I do have experimental settings enabled. Or at least, the checkbox is checked, and I see it in windows-daemon-options.json

And when you do docker info you see lcow graphdriver?

No, I don’t see that option. Is that something separate I need to turn on?

Can you dump your docker info ?
Have you switch on windows containers? —platform=linux is only valid with windows daemon.

Oh, lcow is supported on Windows RS3 (16299) and above only.

Oh, thanks. Good to know I guess.

@ebriney I’m seeing the same error. I am trying docker pull —platform linux registry:2 on Windows.

Oh, lcow is supported on Windows RS3 (16299) and above only.

I don’t get what the number 16299 means. Below is my system. Does it not support —platform linux either?

@chanseokoh 16299 is the build number of your Windows system, here yours is

Hi
Mine is as below but the same issue :
Is there any solution?

I am also getting this error with Windows 10 (17134), which is greater than 16299

I’m on Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950) does that mean I’m screwed.

I think my problem is related. I’m running Windows docker in Windows containers mode and any attempts to use —platform=linux go bust:

This is my docker info , as you can see I’m on Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950):

Источник

TL;DR

I’m on Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950) does that mean I’m screwed???

I think my problem is related. I’m running Windows docker in Windows containers mode and any attempts to use --platform=linux go bust:

PS > docker build --platform=linux --network=host --build-arg sample_TAG=7.0 --rm=true .
Sending build context to Docker daemon  2.048kB
Error response from daemon: unsupported os linux

PS > docker pull --platform=linux jetbrains/teamcity-agent
Using default tag: latest
Error response from daemon: unsupported os linux

This is my docker info, as you can see I’m on Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950):

PS> docker info
Client:
 Debug Mode: false
 Plugins:
  buildx: Build with BuildKit (Docker Inc., v0.3.0-5-g5b97415-tp-docker)
  app: Docker Application (Docker Inc., v0.8.0)

Server:
 Containers: 4
  Running: 0
  Paused: 0
  Stopped: 4
 Images: 6
 Server Version: 19.03.2
 Storage Driver: windowsfilter
  Windows:
 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: hyperv
 Kernel Version: 10.0 17134 (17134.1.amd64fre.rs4_release.180410-1804)
 Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950)
 OSType: windows
 Architecture: x86_64
 CPUs: 12
 Total Memory: 15.8GiB
 Name: LTDY7W2X2
 ID: B5V2:ARDA:HGK4:YMNE:XRS3:C675:SPZK:5X7D:GFHC:UWFQ:JB3O:X4KG
 Docker Root Dir: C:ProgramDataDocker
 Debug Mode: true
  File Descriptors: -1
  Goroutines: 27
  System Time: 2019-09-12T15:59:35.3673461-04:00
  EventsListeners: 1
 HTTP Proxy: http://xxxxx:xxxxx@xxx.xxx.xxx.xxx:xxxx
 HTTPS Proxy: http://xxxxx:xxxxx@xxx.xxx.xxx.xxx:xxxx
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: true
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false
 Product License: Community Engine

Note: LCOW support is currently experimental and under active development.

https://github.com/linuxkit/lcow

Before anything else, it is not yet ready for prime time or work out of the box…

You can check the progress status at https://github.com/moby/moby/issues/33850

Now that it is out of the way, let’s continue:

Requirements

• Windows Server 1709 – Build 16299+
• Hyper-V support, if running on Virtual Machine “Nested Virtualization” must be supported and enabled.

On azure, this means that you MUST use a Dv3 or Ev3 instance (this may be the most important detail you will find here 🙂 )

HowTo

Create Virtual Machine

In the case of Azure, make sure to select an instance size of the latest version (e.g. D2sV3) and Windows Server 2019.

Install Docker EE

Connect to the virtual machine using RDP and on the “DOS prompt” start powershell:

C:UsersFelipe>powershell
 Windows PowerShell
 Copyright (C) Microsoft Corporation. All rights reserved.
 PS C:UsersFelipe>

Install Docker EE using DockerMsftProvider:

Install-Module "DockerMsftProvider" -Force
Update-Module "DockerMsftProvider"
Install-Package Docker -ProviderName "DockerMsftProvider" -Update -Force

You may be prompted to install the NuGet Provider:

NuGet provider is required to continue
 PowerShellGet requires NuGet provider version '2.8.5.201' or newer to interact with NuGet-based repositories. The NuGet
  provider must be available in 'C:Program FilesPackageManagementProviderAssemblies' or
 'C:UsersFelipeAppDataLocalPackageManagementProviderAssemblies'. You can also install the NuGet provider by
 running 'Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force'. Do you want PowerShellGet to install
 and import the NuGet provider now?
 [Y] Yes  [N] No  [S] Suspend  [?] Help (default is "Y"):

Enabled Windows “Containers” Feature

PS C:UsersFelipe> Install-WindowsFeature Containers
 Success Restart Needed Exit Code      Feature Result
 ------- -------------- ---------      --------------
 True    Yes            NoChangeNeeded {}

Most likely you will get the result above indicating that you need to Restart (e.g. Restart = yes). In this case, restart the virtual machine:

Restart-Computer

Reconnect to the Virtual machine using RDP and switch to powershell.

At this point, you should be able to start the docker daemon and even run a windows container on it.

Enable Experimental features

Set-Content -Value "`{`"experimental`":true`}" -Path C:ProgramDatadockerconfigdaemon.json

Start the docker service to check:

PS C:ProgramDatadockerconfig> restart-service docker
 PS C:ProgramDatadockerconfig> docker info
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 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
  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 Datacenter Version 1809 (OS Build 17763.253)
 OSType: windows
 Architecture: x86_64
 CPUs: 2
 Total Memory: 8GiB
 Name: lcow
 ID: ....
 Docker Root Dir: C:ProgramDatadocker
 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

LCOW

Create the directory C:Program FilesLinux Containers:

PS C:> cd 'C:Program Files'
PS C:Program Files> mkdir "Linux Containers"

Download the latest release from https://github.com/linuxkit/lcow/releases

PS C:Program Files> cd '.Linux Containers'
PS C:Program FilesLinux Containers> curl -OutFile release.zip https://github.com/linuxkit/lcow/releases/download/v4.14.35-v0.3.9/release.zip

Expand archive:

PS C:Program FilesLinux Containers> Expand-Archive -DestinationPath . .release.zip

Delete the release.zip file after that:

PS C:Program FilesLinux Containers> rm release.zip

Make sure Hyper-V feature is installed

Install-WindowsFeature Hyper-V –IncludeManagementTools –Restart

You may get disconnected from the virtual machine if a restart is needed. Wait a few seconds and reconnect.

Fun time:

PS C:UsersFelipe> docker run -it --platform=linux busybox echo "LCOW on a Windows Server!" 
LCOW on a Windows Server!

Troubleshooting

Missing Hyper-V

PS C:UsersFelipe> docker run --platform=linux busybox
 Unable to find image 'busybox:latest' locally
 latest: Pulling from library/busybox
 697743189b6d: Pull complete
 Digest: sha256:061ca9704a714ee3e8b80523ec720c64f6209ad3f97c0ff7cb9ec7d19f15149f
 Status: Downloaded newer image for busybox:latest
 C:Program FilesDockerdocker.exe: Error response from daemon: failed to start service utility VM (createreadwrite): CreateComputeSystem 40f05208018c0913e8f8a8f2e770877b96ce64276980a3e1d432849c0d2d8d26_svm: The virtual machine could not be started because a required feature is not installed.

Use a different virtual machine with hardware support for Hyper-V Nested virtualization. In the Azure case, make sure to use a Dv3 or Ev3 instance.

PS C:Program FilesLinux Containers> docker run --platform=linux busybox
 C:Program FilesDockerdocker.exe: Error response from daemon: failed to start service utility VM (createreadwrite): CreateComputeSystem 7e4b0e4ceb834d23bb91293f9c089d1119a6d0c3280306e1586032d1ed10278d_svm: The request is not supported.
 (extra info: {"SystemType":"container","Name":"7e4b0e4ceb834d23bb91293f9c089d1119a6d0c3280306e1586032d1ed10278d_svm","Layers":null,"HvPartition":true,"HvRuntime":{"ImagePath":"C:Program FilesLinux Containers","LinuxInitrdFile":"initrd.img","LinuxKernelFile":"kernel"},"ContainerType":"linux","TerminateOnLastHandleClosed":true}).
 See 'C:Program FilesDockerdocker.exe run --help'.

Missing Hyper-V. Install Hyper-V Windows feature (instructions above).

OS Build not supported

PS C:UsersFelipe> docker run --platform=linux busybox
 Unable to find image 'busybox:latest' locally
 C:Program FilesDockerdocker.exe: Error response from daemon: unsupported os linux.
 See 'C:Program FilesDockerdocker.exe run --help'.

Most likely the Windows Server version doesn’t support LCOW. Check it by running:

PS C:UsersFelipe> docker info
 Containers: 0
  Running: 0
  Paused: 0
  Stopped: 0
 Images: 0
 Server Version: 18.09.2
 Storage Driver: windowsfilter
  Windows:
 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 14393 (14393.2724.amd64fre.rs1_release.181231-1751)
 Operating System: Windows Server 2016 Datacenter Version 1607 (OS Build 14393.2724)
 OSType: windows
 Architecture: x86_64
 CPUs: 2
 Total Memory: 7GiB

The first build to include support was 16299.

Containers Feature not installed

PS C:UsersFelipe> dockerd
 Error starting daemon: failed to load vmcompute.dll, ensure that the Containers feature is installed
 PS C:UsersFelipe>

You need to install docker and the Containers Windows Feature (see previous instructions on how).

Missing platform parameter

PS C:UsersFelipe> docker run busybox
 Unable to find image 'busybox:latest' locally
 latest: Pulling from library/busybox
 C:Program FilesDockerdocker.exe: no matching manifest for unknown in the manifest list entries.
 See 'C:Program FilesDockerdocker.exe run --help'.

Assuming that you have followed all the instructions and everything else is OK, this should simply indicate that you are missing the –platform=linux parameter.

Try again adding –platform=linux after the run:

PS C:UsersFelipe> docker run --platform=linux busybox

Experimental Features disabled

PS C:UsersFelipe> docker run --platform=linux busybox
 "--platform" is only supported on a Docker daemon with experimental features enabled

If after including the platform argument you get the result above you haven’t enabled the docker experimental features.

Missing LCOW (linuxkit)

PS C:ProgramDatadockerconfig> docker run --platform=linux busybox
 Unable to find image 'busybox:latest' locally
 latest: Pulling from library/busybox
 697743189b6d: Pull complete
 Digest: sha256:061ca9704a714ee3e8b80523ec720c64f6209ad3f97c0ff7cb9ec7d19f15149f
 Status: Downloaded newer image for busybox:latest
 C:Program FilesDockerdocker.exe: Error response from daemon: failed to start service utility VM (createreadwrite): kernel 'C:Program FilesLinux Containerskernel' not found.
 See 'C:Program FilesDockerdocker.exe run --help'.

Follow instructions above to download the linuxKit.

References

• https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/linux-containers
• https://stefanscherer.github.io/dockercon-lcow-and-windows-server-1709/
• https://blog.docker.com/2017/09/preview-linux-containers-on-windows/
• https://blog.darrenjrobinson.com/azure-vm-docker-createcontainer-error-0xc0370102/

I have a Windows Server 2022 running on GCP. I’ve installed docker as described here: https://cloud.google.com/compute/docs/containers#docker_on_windows

Namely, I did this:

Install-Module -Name DockerMsftProvider -Repository PSGallery -Force
Install-Package -Name docker -ProviderName DockerMsftProvider
Restart-Computer -Force

However, when I try to run a linux image, I get

PS C:Windowssystem32> docker run busybox ls
Unable to find image 'busybox:latest' locally
latest: Pulling from library/busybox
docker: no matching manifest for windows/amd64 10.0.20348 in the manifest list entries.
See 'docker run --help'.

PS C:Windowssystem32> docker run --rm --platform linux alpine ls
Unable to find image 'alpine:latest' locally
docker: Error response from daemon: unsupported os linux.
See 'docker run --help'.

What am I doing wrong?

Edit. I can’t enable hyper-V on GCP. My processor is Intel(R) Xeon(R) CPU @ 2.80GHz 2.80 GHz should’t it allow nested virtualization

Screenshot

Looks like I need to enable nested virtualization in gcp. For that, I need to set enableNestedVirtualization field to true. There are descriptions on how to do it with gcloud api, but no way I can get my customer to do that. Any way to do it either in the WebUI or the VPS itself?

Edit 2. Does this mean I can’t run a linux docker container from Windows? Or is docker a special case?

L1 VMs have the following restrictions:
You must run Linux-based OSes; you can’t use Windows Server images.

https://cloud.google.com/compute/docs/instances/nested-virtualization/overview

I added this article to my Docker Combat Guide book.

The change of license of Docker Desktop for Windows has been a low punch, a dirty one.

Many big companies use Windows as for the laptops and workstations, we like it or not.

You can setup a Linux development computer or Virtual Machine, you may argue, but things are not as easier.

Big companies have Software licenses assigned to corporation machines, so you may not use your Pycharm license in a Linux VM.

You may no use Docker Desktop either, if your company did not license it.

And finally you may need to have access to internal resources, like Artifactory, or Servers where access is granted via ACL, so only you, from your Development machine can access it. So you have to be able to run Docker locally.

After Docker introduced this changed of license I was using VirtualBox with NAT attached to the VPN Virtual Ethernet, and I port forwarded to be able to SSH, deploy, test, etc… from outside to my Linux VM, and it was working for a while, until with the last VirtualBox update and some Windows updates where pushed to my Windows box and my VirtualBox VMs stopped booting most of the times and having random problems.

I configured a new Linux VM in a Development Server, and I opened Docker API so my Pycharm’s workstation was able to deploy there and I was able to test. But the Dev Ip’s do not have access to the same Test Servers I need my Python Automation projects to reach (and quickly I used 50 GB of space), so I tried WSL. I like Pycharm I didn’t want to switch to VStudio Code because of their good Docker extensions, in any case I could not run my code locally with venv cause some of the packages where not available for Windows, so I needed Linux to run the Unit Testing and see the Code Coverage, run the code, etc…

I tried Hyper-V, tried with NAT External, but it was incompatible with my VPN.

Note: WSL can be used, but I wanted to use Docker Engine, not docker in WSL.

Installing Docker Command line binaries

The first thing I checked was the Docker downloads page.

I found the stand alone binary.

https://docs.docker.com/engine/install/binaries/#install-server-and-client-binaries-on-windows

In order to install it:

1. Download the zip file from the page, in my case docker-20.10.12.zip
   
2. Open PowerShell as Administrator
3. Run: Expand-Archive C:UserscarlesmateoDownloadsdocker-20.10.12.zip  -DestinationPath $Env:ProgramFilesDockerCLI
4. Run: cd $Env:ProgramFilesDockerCLIdocker
5. Run: .dockerd.exe –register-service
6. Run: Start-Service docker
7. Check that Docker lists the running Containers (no errors) with: docker ps
8. Check that the Service is running with: Get-Service docker
   You should expect something like:

Status Name DisplayName
------ ---- -----------
Running docker Docker Engine

Attempt to pull an Image with: docker pull ubuntu or docker pull php

If it works, you’re done, but most probably you will get it starting and get this error:

Error response from daemon: unsupported os linux

or this other error:

no matching manifest for windows/amd64 10.0.19042 in the manifest list entries

Depending on your system you may need to do certain things:

Turn Windows features on or off

I would make sure that are enabled:

• Containers
• Hyper-V
• Virtual Machine Platform
• Windows Hypervisor Platform

Press OK, and restart your computer.

Try Again to docker pull ubuntu

Enable Experimental Mode

Edit this file to enable experimental, you can run from the PowerShell:

notepad C:ProgramDataDockerconfigdaemon.json

Save the file and restart the Service:

Restart-Service docker

Check if it works

Get-Service docker

Status   Name               DisplayName
------   ----               -----------
Running  docker             Docker Engine

Try if now it works.

Switch Daemon

If it is not working, try running:

cd "C:Program FilesDockerDocker"
.DockerCli.exe -SwitchDaemon

Give it two minutes and try to pull an image.

If it is still not working reboot, and try again:

cd "C:Program FilesDockerDocker"
.DockerCli.exe -SwitchDaemon

After it is working

I recommend you to add the new stand alone docker to the path, so you can call it from the terminal at any moment.

Edit the variable PATH of your user profile (not System wide)

I recommend you to have it on top after Python.

LCOW on Edge is not working #4004

Expected behavior

I can pull and run docker containers in windows using LCOW.

Actual behavior

I am unable to pull or run LCOW containers.

Information

• LCOW works fine in docker desktop 2.0.3.0.
• LCOW stopped working when I upgraded to 2.0.4.0 This is when Docker 19.03.0-beta3 was added.
• Windows Version: Windows 10 1803 (OS Build 17134.799)
• Docker for Windows Version: Edge 2.0.4.1 (34207)

The text was updated successfully, but these errors were encountered:

This works ok for me so far.

Ok repro’d this now.

Got confirmation: latest LCOW support requires windows 19.03, you’ll need to update windows.

I see my windows version is 19.03.1 and kernal version is 10.0 17134 but still facing the same issue. Can you please check what can be the issue at my end?

$ docker version
Client: Docker Engine — Community
Version: 19.03.1
API version: 1.40
Go version: go1.12.5
Git commit: 74b1e89
Built: Thu Jul 25 21:17:08 2019
OS/Arch: windows/amd64
Experimental: true

Server: Docker Engine — Community
Engine:
Version: 19.03.1
API version: 1.40 (minimum version 1.24)
Go version: go1.12.5
Git commit: 74b1e89
Built: Thu Jul 25 21:25:07 2019
OS/Arch: windows/amd64
Experimental: true

$ docker info
Client:
Debug Mode: false
Plugins:
app: Docker Application (Docker Inc., v0.8.0)
buildx: Build with BuildKit (Docker Inc., v0.2.2-10-g3f18b65-tp-docker)

Источник

LCOW: Linux Containers on Windows Server

Published by Felipe Crochik on February 16, 2019 February 16, 2019

Recent Posts

Archives

Note: LCOW support is currently experimental and under active development.

Before anything else, it is not yet ready for prime time or work out of the box…

Now that it is out of the way, let’s continue:

Requirements

• Windows Server 1709 – Build 16299+
• Hyper-V support, if running on Virtual Machine “Nested Virtualization” must be supported and enabled.

On azure, this means that you MUST use a Dv3 or Ev3 instance (this may be the most important detail you will find here 🙂 )

HowTo

Create Virtual Machine

In the case of Azure, make sure to select an instance size of the latest version (e.g. D2sV3) and Windows Server 2019.

Install Docker EE

Connect to the virtual machine using RDP and on the “DOS prompt” start powershell:

Install Docker EE using DockerMsftProvider:

You may be prompted to install the NuGet Provider:

Enabled Windows “Containers” Feature

Most likely you will get the result above indicating that you need to Restart (e.g. Restart = yes). In this case, restart the virtual machine:

Reconnect to the Virtual machine using RDP and switch to powershell.

At this point, you should be able to start the docker daemon and even run a windows container on it.

Enable Experimental features

Start the docker service to check:

Create the directory C:Program FilesLinux Containers:

Delete the release.zip file after that:

Make sure Hyper-V feature is installed

You may get disconnected from the virtual machine if a restart is needed. Wait a few seconds and reconnect.

Fun time:

Troubleshooting

Missing Hyper-V

Use a different virtual machine with hardware support for Hyper-V Nested virtualization. In the Azure case, make sure to use a Dv3 or Ev3 instance.

Missing Hyper-V. Install Hyper-V Windows feature (instructions above).

OS Build not supported

Most likely the Windows Server version doesn’t support LCOW. Check it by running:

The first build to include support was 16299.

Containers Feature not installed

You need to install docker and the Containers Windows Feature (see previous instructions on how).

Missing platform parameter

Assuming that you have followed all the instructions and everything else is OK, this should simply indicate that you are missing the –platform=linux parameter.

Try again adding –platform=linux after the run:

Experimental Features disabled

If after including the platform argument you get the result above you haven’t enabled the docker experimental features.

Missing LCOW (linuxkit)

Follow instructions above to download the linuxKit.

References

james · April 29, 2019 at 2:46 am

how to run linux containers in AWS windows server 2019 base datacenter edition as i have followed this blog to run LCOW in AWS windows server 2019 and was through “Error response from daemon: failed to start service utility VM (createreadwrite): CreateComputeSystem 500857995b75ae7b7cb918dd32fc032f7a851004d31d60ee1b544e12b34bfc9b_svm: The virtual machine could not be started because a required feature is not installed.” Any suggestions. Thanks

Felipe Crochik · May 1, 2019 at 6:17 am

Hi James. I haven’t tried this on AWS. Have you checked that nested virtualization is supported on the instance you created?

SGP · December 13, 2019 at 6:44 pm

I am currently facing the same issue described by James while using Windows Server 2019 on AWS.
I was expecting this to work just fine with a recent Hyper-V AMI (AMI ID: ami-0127ee9a754557b67 – Windows_Server-2019-English-Full-HyperV-2019.11.13), but when attempting to run a Linux Docker image I am getting the same error.

C:UsersAdministrator>docker run -ti –isolation=hyperv 84120c6c3491
docker: Error response from daemon: failed to start service utility VM (createreadwrite): hcsshim::CreateComputeSystem c5185a5d19859af629d4b383a1c53b3e173748ca102430c47edcf9f11cb926c1_svm: The virtual machine could not be started because a required feature is not installed.
(extra info: <“SystemType”:”container”,”Name”:”c5185a5d19859af629d4b383a1c53b3e173748ca102430c47edcf9f11cb926c1_svm”,”Layers”:null,”HvPartition”:true,”HvRuntime”:<“ImagePath”:”C:\Program Files\Linux Containers”,”LinuxInitrdFile”:”initrd.img”,”LinuxKernelFile”:”kernel”>,”ContainerType”:”linux”,”TerminateOnLastHandleClosed”:true>).

Any ideas would be greatly appreciated.

I have reviewed the installed Windows components, docker packages, experimental features, default platform, etc., set, re-set, rebooted, … still no joy.

SGP · December 13, 2019 at 6:47 pm

oops… my last example includes the “–issolation=hyperv” parameter on “docker run”… this was just another experiment. I copied the wrong example.

This same behavior happens without this parameter included which is my expected scenario.

Indian Velumani · December 17, 2019 at 3:21 am

I tried like and I got error like this.
In Windows 2016 server std.

C:Program FilesDockerdocker.exe: failed to register layer: failed to start service utility VM (applydiff e8e51d13ddc7
93adab0dad0972c8ccba89df623886232a4df37553c5a10248c0): container e8e51d13ddc793adab0dad0972c8ccba89df623886232a4df37553c
5a10248c0_svm encountered an error during CreateContainer: failure in a Windows system call: The data is invalid. (0xd)
extra info: <“SystemType”:”container”,”Name”:”e8e51d13ddc793adab0dad0972c8ccba89df623886232a4df37553c5a10248c0_svm”,”Lay
ers”:null,”HvPartition”:true,”HvRuntime”: <“ImagePath”:”C:\Program Files\Linux Containers”,”LinuxInitrdFile”:”initrd.im
g”,”LinuxKernelFile”:”bootx64.efi”>,”ContainerType”:”linux”,”TerminateOnLastHandleClosed”:true>.

Indian Velumani · December 17, 2019 at 3:26 am

I tried in windows 2016 server std edition
But I got like this, Any idea to resolve this.

C:Program FilesDockerdocker.exe: failed to register layer: failed to start service utility VM (applydiff e8e51d13ddc7
93adab0dad0972c8ccba89df623886232a4df37553c5a10248c0): container e8e51d13ddc793adab0dad0972c8ccba89df623886232a4df37553c
5a10248c0_svm encountered an error during CreateContainer: failure in a Windows system call: The data is invalid. (0xd)
extra info: <“SystemType”:”container”,”Name”:”e8e51d13ddc793adab0dad0972c8ccba89df623886232a4df37553c5a10248c0_svm”,”Lay
ers”:null,”HvPartition”:true,”HvRuntime”: <“ImagePath”:”C:\Program Files\Linux Containers”,”LinuxInitrdFile”:”initrd.im
g”,”LinuxKernelFile”:”bootx64.efi”>,”ContainerType”:”linux”,”TerminateOnLastHandleClosed”:true>.

nedumaran · April 21, 2020 at 5:58 am

Hi Velumani, i am also facing the same error that you face. Just wanted to check if you were able to fix this. if so, could you please share the solution for this error?

Источник

LCOW: Invalid Platform OS «linux» #2241

Expected behavior

Build a Linux image for CentOS 6.8 while using Windows containers

Actual behavior

Unable to pull the image or build.
Returns an error saying:

Error response from daemon: invalid platform: invalid platform os «linux»

Information

• Windows Version: Windows 10 Enterprise Version 10.0.14393 Build 14393
• Docker for Windows Version: Version 18.03.0-ce-win59 (16762)

I’m working on a project that requires running both Linux containers and Windows containers at the same time. I’m not using the most recent version of Docker in this channel, because that version crashes whenever I switch to Windows containers (#1898).

Steps to reproduce the behavior

1. Start Docker for Windows
2. Switch to using Windows containers
3. Enable Experimental features in the Docker settings
4. In command line, run docker pull —platform=linux centos:6.8

The text was updated successfully, but these errors were encountered:

Downloaded 18.03.0-ce-win72 and now I just get an «unsupported os linux»

Has the experimental feature been removed?

Hi @necroTaxonomist. Yes, you have to enable experimental in the daemon settings. We disabled it because if you pull an lcow image and disable experimental, it bricks your windows daemon.

@ebriney I do have experimental settings enabled. Or at least, the checkbox is checked, and I see it in windows-daemon-options.json

And when you do docker info you see lcow graphdriver?

No, I don’t see that option. Is that something separate I need to turn on?

Can you dump your docker info ?
Have you switch on windows containers? —platform=linux is only valid with windows daemon.

Oh, lcow is supported on Windows RS3 (16299) and above only.

Oh, thanks. Good to know I guess.

@ebriney I’m seeing the same error. I am trying docker pull —platform linux registry:2 on Windows.

Oh, lcow is supported on Windows RS3 (16299) and above only.

I don’t get what the number 16299 means. Below is my system. Does it not support —platform linux either?

@chanseokoh 16299 is the build number of your Windows system, here yours is

Mostafa-Armandi commented Aug 26, 2019

Hi
Mine is as below but the same issue :
Is there any solution?

I am also getting this error with Windows 10 (17134), which is greater than 16299

fernandoespinosa commented Sep 12, 2019 •

I’m on Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950) does that mean I’m screwed.

I think my problem is related. I’m running Windows docker in Windows containers mode and any attempts to use —platform=linux go bust:

This is my docker info , as you can see I’m on Operating System: Windows 10 Enterprise Version 1803 (OS Build 17134.950):

Источник

Mixing Windows and Linux containers with Docker Compose

Premier Developer Consultant Randy Patterson explores how to mix Windows and Linux containers with Docker Compose.

Running Linux containers on a Windows host has been available for awhile now. However, getting Windows and Linux containers to communicate without Docker Compose results in using the containers’ IP Addresses. This is not a good solution since container IP Addresses change often. A better solution is to take advantage of the Docker Compose networking and use the service name instead of the IP address. A Windows host has no problem running Linux containers but Docker Compose does not automatically support multi-platform hosts.

The platform configuration option was added to Docker Compose files starting with version 2.4 and then removed beginning with version 3.x. It is a know bug and the expectation is that the platform option will return soon. When this article was written, it has not yet appeared in version 3.x so we will continue to use file format version 2.4 for our Docker Compose yaml files.

Setting up your environment

Running Linux containers on Windows and platform support in Docker Compose requires Windows 1803 or greater. I am running Windows 10 1809.

In addition, you must be running the latest version of Docker for Windows and have the experimental features enabled.

If you are running different versions of Windows or Docker your mileage may vary.

Source Code

Next, grab the source code located in the GitHub repo here containing two solutions

1. Webtier.sln – Asp.Net MVC application running .NET Framework 4.6.x and a Dockerfile for creating a Windows image hosting IIS.
2. ApiTier.sln – Asp.Net Core 2.1 application and a Dockerfile for creating a Linux image to host the application

The application is a simple web page that displays the hostname of the Web Tier then calls the API Tier to get and display the API hostname. When running in containers, the container Id is displayed. Your Id’s will be different

Docker-Compose

The docker-compose.yml file, located in the root of the solution, adds the platform: windows parameter to the webtier service and the platform: linux parameter to the apitier service.

Next, bring up the multi-container, multi-platform application using docker-compose. Start a powershell prompt in the solutions root folder, the same folder that contains the docker-compose.yml file. Type the command:

Docker Compose will create the images if they do not already exist, then create the virtual network to host the containers and finally start the containers in the correct order.

Finally, retrieve the host port of the webtier container

Use your browser to navigate to http://localhost:38736 (your port number will be different)

If the Windows Web Tier was able to communicate with the Linux API Tier, you will see the id for each of the containers (your id’s will be different) on the web page.

Using the platform option in your configuration files allows Docker Compose to mix Windows and Linux containers when hosted on a multi-platform host like Windows. Keep in mind that this is an experimental feature and is not yet ready for production environments.

Developer Support App Dev Customer Success Account Manager, Microsoft Developer Support

Read next

Hi,
a very nice article.
I am using LCOW for several months and it works for integration tests ina mixed environment very well.But now I have a problem using microsoft/dotnet:2.2-aspnetcore-runtime(or …-alpine) for the linux images.
Building the docker image on linux with this base image and running it in anLCOW environment works in that way that the container starts and itsfunctions are available.
But if I want to stop the container it takes several minutes to stop thecontainer.
Do you have any idea why it takes so long?
Best regardsChristian

Thanks for the comment Christian. LCOW containers taking a long time to stop is a known issue that hasn’t been fixed yet. I don’t always experience it with ‘docker stop’ but I do with ‘docker-compose down’. Just be patient for now and don’t kill the process. ‘docker-compose down’ will also remove the network it created and if that gets interupted it can be difficult to fix.

Источник

I would like to run Windows and Linux platform containers side by side using docker-compose.yml by utilising the platform property of dockers experimental mode.

However when I specify the linux platform for a container I am shown the error «Error response from daemon: unsupported os linux».

I used the following docker-compose.yml to replicate this issue:

version: "4.12"
services:
  app:
    image: mcr.microsoft.com/windows/servercore/iis:windowsservercore-ltsc2019
    container_name: application
    ports:
      - 8000:80
  db:
    image: mysql:5.7
    platform: linux
    container_name: database
    restart: unless-stopped
    environment:
      MYSQL_DATABASE: db_name
      MYSQL_ROOT_PASSWORD: secret
      MYSQL_PASSWORD: secret
      MYSQL_USER: db_user
    ports:
      - "3306:3306"

• I have tried with the latest version of Docker Desktop
• I have tried disabling enabled experimental features
• I have uploaded Diagnostics
• Diagnostics ID:

Actual behavior

If I run docker compose up the console outputs the following error:

C:Devdockertesting-dual-os-containers>docker compose up
[+] Running 0/0
 - db Error     0.1s
 - app Error   0.1s
Error response from daemon: unsupported os linux

Expected behavior

Running docker compose up should start up both containers, one on the windows platform and the other on linux.

Information

I switched Docker to Windows containers by right clicking the tray icon and selecting ‘Switch to Windows containers…’
I have enabled experimental features in docker by setting the Docker Engine to the following:

{
  "builder": {
    "gc": {
      "defaultKeepStorage": "20GB",
      "enabled": true
    }
  },
  "experimental": true,
  "features": {
    "buildkit": true
  }
}

I restarted docker desktop after enabling experimental mode.

• Windows Version: 21H2
• Docker Desktop Version: v4.12.0
• WSL2 or Hyper-V backend? ESL2
• Are you running inside a virtualized Windows e.g. on a cloud server or a VM: No

Output of & "C:Program FilesDockerDockerresourcescom.docker.diagnose.exe" check

[2022-12-02T10:22:21.457561400Z][com.docker.diagnose.exe][I] set path configuration to OnHost
Starting diagnostics

[PASS] DD0027: is there available disk space on the host?
[PASS] DD0028: is there available VM disk space?
[PASS] DD0031: does the Docker API work?
[PASS] DD0004: is the Docker engine running?
[PASS] DD0011: are the LinuxKit services running?
[PASS] DD0016: is the LinuxKit VM running?
[PASS] DD0001: is the application running?
[SKIP] DD0018: does the host support virtualization?
[PASS] DD0002: does the bootloader have virtualization enabled?
[PASS] DD0017: can a VM be started?
[PASS] DD0023: is the Containers Windows Feature enabled?
[PASS] DD0015: are the binary symlinks installed?
[PASS] DD0003: is the Docker CLI working?
[PASS] DD0013: is the $PATH ok?
[PASS] DD0005: is the user in the docker-users group?
[PASS] DD0007: is the backend responding?
[FAIL] DD0014: are the backend processes running? 1 error occurred:
        * vpnkit.exe is not running


[PASS] DD0008: is the native API responding?
[PASS] DD0009: is the vpnkit API responding?
[PASS] DD0010: is the Docker API proxy responding?
[PASS] DD0006: is the Docker Desktop Service responding?
[PASS] DD0012: is the VM networking working?
[PASS] DD0032: do Docker networks overlap with host IPs?
[SKIP] DD0030: is the image access management authorized?
[PASS] DD0033: does the host have Internet access?

Please investigate the following 1 issue:

1 : The test: are the backend processes running?
    Failed with: 1 error occurred:
        * vpnkit.exe is not running



Not all of the backend processes are running.

Steps to reproduce the behavior

1. Create a docker-compose.yml file in a directory and paste in the contents of the docker-compose.yml specified above
2. In a terminal run docker compose up from the directory that contains the docker-compose.yml file, this should produce the console output described in ‘Actual behaviour’