Arthur T Knackerbracket has found the following story:
Experimental support for Microsoft's Linux containers on Windows (LCOW) feature has been available for Windows Server 1709 via the Docker EE "Preview" release. The same functionality is now available for Windows 10 Fall Creators Update with the release of Docker for Windows 17.11. In fact, it's been available since Docker for Windows 17.10.
That's right. Docker for Windows can run Linux or Windows containers, with support for Linux containers via a Hyper-V Moby Linux VM (as of Docker for Windows 17.10 this VM is based on LinuxKit).
When configured to use Linux containers for Windows, try running a simple Linux container:
When disabled, the existing options for switching between traditional Docker for Windows Linux containers and Windows containers will be available in the whale systray icon.
The LCOW feature is under active development.
(Score: 2, Insightful) by Anonymous Coward on Sunday November 26 2017, @11:02PM
It's a trap!!!!
(Score: 4, Insightful) by ealbers on Sunday November 26 2017, @11:09PM
Great I can run a supercomputer OS on a desktop which crashes all the time
Fabulous what could possibly go wrong
(Score: 4, Touché) by ealbers on Sunday November 26 2017, @11:11PM
and it'll be awesome!
(Score: 1, Interesting) by Anonymous Coward on Sunday November 26 2017, @11:16PM
Now brought to you by hybrid exploits.
(Score: 5, Insightful) by Anonymous Coward on Sunday November 26 2017, @11:49PM (1 child)
If I want to use Linux - and I do - I'm not doing via Windows anything. So thanks for the offer Microsoft, but no thanks.
(Score: 3, Insightful) by digitalaudiorock on Monday November 27 2017, @11:46PM
...and if I wanted Windows with my Linux I'd just use systemd. (ducks).
(Score: 3, Interesting) by goodie on Monday November 27 2017, @12:43AM (1 child)
See the other day I wanted to be a hipster and try a Docker VM from a vendor and I was unable to run the installer on Win7. So no thank you.
(Score: 3, Informative) by isostatic on Monday November 27 2017, @03:50PM
Your first mistake is running windows - really? 2000 called and wanted its OS back.
(Score: 4, Interesting) by RamiK on Monday November 27 2017, @01:04AM (2 children)
...gone full retard.
Seriously, I get this might scrape you the odd customer off the bottom of the linux barrel... But just how many engineer-hours have went into this zero-added-value VM abstraction layer?
Such a waste.
compiling...
(Score: 2) by DannyB on Monday November 27 2017, @04:58PM (1 child)
Microsoft thinks it can sell this to the decision makers. By offering them discounts such that using Windows would be only triple the cost of using Linux.
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.
(Score: 2) by RamiK on Wednesday November 29 2017, @12:16AM
But that's what Hyper-V Docker containers already offered. Going through the WSL only hurts security by removing the isolation while laboring Microsoft's engineering staff with maintaining, optimizing and securing yet another, foreign API layer. They're literally adding nothing new to their product portfolio...
compiling...
(Score: 2) by Gaaark on Monday November 27 2017, @01:50AM
It's like seeing those inflatable Darth Vaders on peoples front lawns for celebrating Christmas:
NOTHING says Christmas like Darth Vader, and being able to run linux on windows.
Peoples is dumb.
--- Please remind me if I haven't been civil to you: I'm channeling MDC. ---Gaaark 2.0 ---
(Score: 2) by Arik on Monday November 27 2017, @02:06AM (2 children)
If laughter is the best medicine, who are the best doctors?
(Score: 0) by Anonymous Coward on Monday November 27 2017, @02:14AM
Relevant files in proc that provide inspection of bios and CPU maybe
(Score: 3, Funny) by Anonymous Coward on Monday November 27 2017, @01:17PM
Measure the average time between reboots? :-)
(Score: 1, Funny) by Anonymous Coward on Monday November 27 2017, @07:02AM
Hi perv!
(Score: 0) by Anonymous Coward on Monday November 27 2017, @01:15PM
Given that Windows 17.11 is not only not yet out, but that there are no indications that such a Windows version will ever exist, why would I want to get Docker for it? :-)
(Score: 0) by Anonymous Coward on Monday November 27 2017, @03:02PM (1 child)
of something called "stockholm syndrom".
(Score: 2) by DannyB on Monday November 27 2017, @05:00PM
Shhhhh! The code name is supposed to be for internal use only!
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.
(Score: 2) by meustrus on Monday November 27 2017, @05:01PM
Plenty of corporate environments still use Windows as the base OS. Microsoft's enterprise management tools are the One Way to manage authentication, sharing, and communication in many places. So you may not have a choice of OS on your developer workstation, even if your software is going to run exclusively in Linux.
The idea here isn't that you are going to run a Docker environment to get a Linux workstation inside Windows. You could already do that with VirtualBox, sans Docker. What this does is let you debug your Linux Docker container on your local workstation (which is locked to Windows because of your enterprise) before shipping it to the cloud.
In short, Linux containers running on Windows is great for cloud developers that are forced by the enterprise to run Windows.
If there isn't at least one reference or primary source, it's not +1 Informative. Maybe the underused +1 Interesting?
(Score: 2) by DannyB on Monday November 27 2017, @05:04PM
With Windows Subsystem for Linux, it is possible1 to run2 Linux executables directly on Windows. The Windows Kernel emulates the Linux kernel ABI for these executables.
With such a capability, why isn't Microsoft using Windows Subsystem for Linux to run its Docker? Have they not thought of that?
1but why not just use a genuine Linux kernel and avoid potential incompatibilities?
2between reboots and blue screams
To transfer files: right-click on file, pick Copy. Unplug mouse, plug mouse into other computer. Right-click, paste.