Support for running on Windows using Linux Containers for Windows (LCOW)

[gbraad]

FEATURE REQUEST

This is not the same as #2015. As mentioned in the article https://www.hanselman.com/blog/DockerAndLinuxContainersOnWindowsWithOrWithoutHyperVVirtualMachines.aspx by Scott Hanselman, there is a new functionality to run Linux Containers on Windows (LCOW). As part of the Windows 10 Pro 1709 and the Docker edge release, it is possible to activate "Linux Containers on Windows", which would make it maybe possible to target the container runtime that would run in/on Windows, such as minikube start --vm-driver windows.

The issue for Windows Containers , as mentioned before, is not the same as mentioned by Scott. Windows Containers is running Windows-based ones on Windows. This is about running Linux containers on Windows (without the MobylinuxVM). It describes a use-case that is closer to the none driver currently used to target a local Docker daemon. With the suggested windows, it would indicate to target the Linux container runtime on Windows (v1709).

Requirements

• Insider build of Windows (1709)
  https://insider.windows.com/en-us/
• Docker for Windows (edge channel)
  https://download.docker.com/win/edge/Docker%20for%20Windows%20Installer.exe

References

• Proposal: LCOW Support containerd/containerd#1185
• https://cloudblogs.microsoft.com/hybridcloud/2017/04/18/dockercon-2017-powering-new-linux-innovations-with-hyper-v-isolation-and-windows-server/
• https://blog.docker.com/2017/09/preview-linux-containers-on-windows/

[gbraad]

@aaron-prindle this...

---

However, "Linux Containers on Windows" (LCOW) does not support "privileged mode" => nodeshift/nodeshift#127 (minishift/minishift#1588 (comment))

C:\Users\gbraad>docker run -it --privileged --pid=host gbraad/hostenter /bin/sh
docker: Error response from daemon: Windows does not support privileged mode.

• namespacing issues
• no shared host folders?

and likely more...

As I can see, it works by using a very small runtime when instantiating a container. It does this with the aid of:

PS C:\Users\gbraad> cd "$env:ProgramFiles\Linux Containers"
PS C:\Program Files\Linux Containers> ls


    Directory: C:\Program Files\Linux Containers


Mode                LastWriteTime         Length Name
----                -------------         ------ ----
-a----       11/26/2017   2:27 PM        6927120 bootx64.efi
-a----       11/26/2017   2:27 PM        7038899 initrd.img

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[bardware]

/remove-lifecycle rotten

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
/remove-lifecycle stale

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close