-
Notifications
You must be signed in to change notification settings - Fork 18.7k
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
Epic: Linux Containers on Windows (LCOW) #33850
Comments
What would be a usecase of "Cross-platform multi stage builds"? |
@AkihiroSuda It would be great for cross platform builds. For example, if you had a collection of bash scripts and a language with cross-compilation support like golang, then you could actually build your code in Linux then copy the binaries into a |
Is the mentioned v2 API related to WSL 2 announced recently for Windows Insiders and to Docker preview, which shall be available in July? |
WSL2 uses some of the HCS v2 APIs. But no, there's no relation as such between LCOW in moby and WSL2. |
So Linux containers support in Docker preview (which is not yet available) is something different to experimental LCOW in moby from this Epic? |
If you're referring to Docker for Windows, currently it can use this LCOW rather than moby VM as an experimental feature in D4W, but I understand "they" (folks at Docker Inc) are working on an alternate solution using WSL2. |
@jhowardmsft regarding Docker announcement for WSL2, does it mean LCOW is going to die and be replaced by WSL2 support if conclusive? |
@jhowardmsft Yes, I am referring to https://engineering.docker.com/2019/06/docker-hearts-wsl-2/, which is announced by Docker Inc folks. Anyway, using either solution (MS LCOW or Docker WSL2) will be great improvement over Samba connection to local files (in sense of reliability). |
Hi, is there a time line for a stable GA of LCOW? |
LCOW support is still experimental, and the current implementation is not recommended for serious work as there's still many features missing, and quite some known bugs/limitations; the current will be removed at some point (Active work is ongoing to re-implement LCOW at the runtime level through containerd). If your use-case is to run Linux containers on a Windows machine, you might be interested in the tech preview of Docker Desktop for WSL2; |
@thaJeztah do you know if there is any alternative (in beta, planned or otherwise) to manage Windows and Linux containers simultaneously without engine switching? WSL2 builds do not allow this at the moment and behave similarly to "Use Linux containers" mode. That's the main use case for us at the moment, and it's unclear how if at all this will be supported in the future. |
@thaJeztah do you know how to run Linux container on Windows (LCOW), with --network=transparent.
But ran into the below mentioned issue, after running the above command -
|
I am quite confused with the strategy of providing the Linux container support on Windows. I have Heard alot about LCOW and WSL to run linux container but I am still not sure why they are not providing the support of Linux Container using MOBY VM as in WIN 10 till things are not stable ( ie till LCOW is no more an experimental thing). There seems to be no fix strategy for the support of Linux containers on server 2016 and 2019. In server 2019 I have no other way except running linux container as LCOW and that is experimental. On server 2016 there is another issue if I run docker for win on it I don't get the support of the latest Docker builds as the new versions of Docker are not supported. |
I would dare to say that the general perception is to use linux servers for linux containers (in production). LCOW and Moby are more developer tools than production tools. |
One could not directly say that running Linux containers on Windows Environment is a wrong Strategy. Windows itself is putting efforts in this direction but the problem is that things are not clear. We also have client constraints that puts us to Windows Route |
I agree that for servers, I see nothing from Microsoft or Docker to
indicate that “Linux on Windows” is a strategy. If you see documentation
indicating otherwise, please let me know. The strategy for both sides for
years now has been to make it easier for both windows and Linux containers
on windows 10 only.
…On Thu, Oct 3, 2019 at 4:48 AM Shubhanshu Rastogi ***@***.***> wrote:
I am quite confused with the strategy of providing the Linux container
support on Windows. I have Heard alot about LCOW and WSL to run linux
container but I am still not sure why they are not providing the support of
Linux Container using MOBY VM as in WIN 10 till things are not stable ( ie
till LCOW is no more an experimental thing). There seems to be no fix
strategy for the support of Linux containers on server 2016 and 2019. In
server 2019 I have no other way except running linux container as LCOW and
that is experimental. On server 2016 there is another issue if I run docker
for win on it I don't get the support of the latest Docker builds as the
new versions of Docker are not supported.
As there no solid way to run LINUX container on server 2016 and server
2019 that always works with no issues.
I would dare to say that the general perception is to use linux servers
for linux containers (in production). LCOW and Moby are more developer
tools than production tools.
One could not directly say that running Linux containers on Windows
Environment is a wrong Strategy. Windows itself is putting efforts in this
direction but the problem is that things are not clear. We also have client
constraints that puts us to Windows Route
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#33850?email_source=notifications&email_token=AAGBNX2EAFPAHLQV3TJCMNDQMWWXBA5CNFSM4DQ3YDWKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEAHPD2Q#issuecomment-537850346>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGBNX7EJXLXBC4URLN3U6TQMWWXBANCNFSM4DQ3YDWA>
.
|
just a quick note - I haven't been tracking status of this since I changed teams early last year and am focusing on Kubernetes work. I'm looking for someone to give an update on what's next. Personally I'm quite happy using WSL2 for development since I can build, test and run Linux code there including Moby, ContainerD and Kubernetes. |
There was no update to vendor.conf (opengcs, hcsshim) for 7 months now. Is there anything to show to public, please? |
Linux Containers on Windows development moved to ContainerD, and no more work is happening in the Moby codebase. I don't think we need to keep this epic open any longer since there's no progress tracked here. cc @mamezgeb |
Microsoft is hard at work adding support to run both Windows & Linux containers side by side on the same node with a single Docker daemon. As Linux containers are launched, Hyper-V will be used to boot and run a Linux kernel which will then be used to host the container natively. Because many areas of Docker will require changes to handle running multiple platforms side by side, we'll be using this epic to track the list of PRs and proposals in a single place.
Preview documentation
https://docs.microsoft.com/en-us/virtualization/windowscontainers/deploy-containers/linux-containers
Progress
Required for Docker for Windows - Developer Scenarios
docker commit
,docker cp
, andDockerfile
ADD
commands--platform
parameter fordocker run
,docker pull
,docker import
anddocker build
to choose between platforms and order of precedence when multiple are supported (Windows & Linux) on the same node. See Proposal #34617 .docker kill -s
for signals != SIGKILL.WORKDIR
in running existing images and building new onesdocker search
anddocker images
docker run --user
seems to be ignored #36469Required for Kubernetes
docker stats
for multiple platformsdocker info
& daemon configuration to show what platforms each node is capable of, and restrict to single platforms if neededRequired for Swarm
--platform
flag support todocker-compose
, anddocker stack deploy
docker stats
for multiple platformsdocker volume
commandsdocker service create --no-resolve-image
as a workaroundBacklog, need to set priority
docker top
docker run
flags. Feedback welcome on what's needed vs notdocker export
,docker import
,docker save
need platform flagsCOPY
command inDockerfile
Glossary & References
There's a brief description of gcs & hcs from a Dockercon 2016 presentation
FAQs
What's needed to fully test this?
The text was updated successfully, but these errors were encountered: