11–20 of 22 posts
I was expecting LCOW to not need Hyper-V at all and to use Windows' WSL. I thought it was the whole point behind WSL -- to beta-test Linux containers support without the need for virtualization.
Earlier quoted context omitted.
any idea what host windows OS are supported? I suppose only those with hyper-v.
I’m looking for the same answer. I expect you are right, as the MS article linked does talk about some Hyper-V capabilities leveraged by LinuxKit (even though MobyLinux is no longer running as a HyperV VM).
I was expecting LCOW to not need Hyper-V at all and to use Windows' WSL. I thought it was the whole point behind WSL -- to beta-test Linux containers support without the need for virtualization.
Hyper-V virtualization requirements are removed with this update. It does rely on Hyper-V isolation, which appears to have more in common with Linux namespaces than virtualization. Virtualization isn’t completely off the table. The article mentions a minimal, LinuxKit-based hypervisor. I may be off, but I’m imagining something more akin to what’s happening on macOS via HyperKit.
So I have 2 questions still: - On a windows server can I run a Linux container? - On Windows server can I run a Windows container and a Linux container side by side?
So I have 2 questions still: - On a windows server can I run a Linux container? - On Windows server can I run a Windows container and a Linux container side by side?
I think we will be able run them together in the future.
I was expecting LCOW to not need Hyper-V at all and to use Windows' WSL. I thought it was the whole point behind WSL -- to beta-test Linux containers support without the need for virtualization.
Hyper-V virtualization requirements are removed with this update. It does rely on Hyper-V isolation, which appears to have more in common with Linux namespaces than virtualization. Virtualization isn’t completely off the table. The article mentions a minimal, LinuxKit-based hypervisor. I may be off, but I’m imagining something more akin to what’s happening on macOS via HyperKit.
I was expecting LCOW to not need Hyper-V at all and to use Windows' WSL. I thought it was the whole point behind WSL -- to beta-test Linux containers support without the need for virtualization.
Docker for Windows already runs Linux containers. This is an update: "The setup for running Linux containers with LCOW is a lot simpler than the previous architecture where a Hyper-V Linux VM runs a Linux Docker daemon, along with all your containers. With LCOW, the Docker daemon runs as a Windows process (same as when running Docker Windows containers), and every time you start a Linux container Docker launches a mi…
any idea what host windows OS are supported? I suppose only those with hyper-v.
Docker for Windows already runs Linux containers. This is an update: "The setup for running Linux containers with LCOW is a lot simpler than the previous architecture where a Hyper-V Linux VM runs a Linux Docker daemon, along with all your containers. With LCOW, the Docker daemon runs as a Windows process (same as when running Docker Windows containers), and every time you start a Linux container Docker launches a mi…
This is a major update as now the Docker daemon runs as a Windows process, not as a Linux process. One VM/container is also a huge change. Before this, you had to manage a single VM that runs all the containers, allocate memory and CPU for that whole VM, assign Hyper-V virtual switch(es) to that VM. Basically this intends to bring Linux containers to Windows Server.
Earlier quoted context omitted.
Hyper-V virtualization requirements are removed with this update. It does rely on Hyper-V isolation, which appears to have more in common with Linux namespaces than virtualization. Virtualization isn’t completely off the table. The article mentions a minimal, LinuxKit-based hypervisor. I may be off, but I’m imagining something more akin to what’s happening on macOS via HyperKit.
Not quite. It doesn’t use the existing Hyper-V management stack, but it does use the Hyper-V hypervisor and (trimmed down) virtual device stack.
I'm just curious because sometimes it messes with your video card driver.