New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
gbraad opened this Issue Nov 26, 2017 · 7 comments

Comments

Projects
None yet
4 participants
@gbraad
Collaborator

gbraad commented Nov 26, 2017

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.

image_7702d8a0-6b78-449d-9b7b-cf9a34b080c3

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

References

@gbraad

This comment has been minimized.

Show comment
Hide comment
@gbraad

gbraad Nov 26, 2017

Collaborator

@aaron-prindle this...


However, "Linux Containers on Windows" (LCOW) does not support "privileged mode" => bucharest-gold/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
Collaborator

gbraad commented Nov 26, 2017

@aaron-prindle this...


However, "Linux Containers on Windows" (LCOW) does not support "privileged mode" => bucharest-gold/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

@gbraad gbraad changed the title from Support for running on Windows using Linux Containers for Windows to Support for running on Windows using Linux Containers for Windows (LCOW) Nov 26, 2017

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Feb 25, 2018

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 commented Feb 25, 2018

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

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Mar 27, 2018

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 commented Mar 27, 2018

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

This comment has been minimized.

Show comment
Hide comment
@bardware

bardware Mar 27, 2018

/remove-lifecycle rotten

bardware commented Mar 27, 2018

/remove-lifecycle rotten

@fejta-bot

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Jun 25, 2018

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 commented Jun 25, 2018

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

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Jul 25, 2018

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 commented Jul 25, 2018

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

This comment has been minimized.

Show comment
Hide comment
@fejta-bot

fejta-bot Aug 24, 2018

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

fejta-bot commented Aug 24, 2018

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment