Isn't that why it requires Hyper-V?
There's reference in the instructions that changing the IPs will require the VM to be rebooted from what I can tell as well.
Similarly, I use Veertu on OS X: it uses the inbuilt VM in OS X but it's still using a VM.
The title of this article is inaccurate.
So, yes Microsoft did implement containers in the Windows kernel, but that isn't what OP is about.
[0]:https://msdn.microsoft.com/en-us/virtualization/windowsconta...
Its the same as the Docker for macOS, where is is booting a VM in the background, you just can't see it.
* https://blog.docker.com/2016/09/build-your-first-docker-wind... * https://blog.docker.com/2016/09/dockerforws2016/
As someone that develops software for Windows since the version 3.1, I don't get why professional developers would use the consumer version of Windows.
Because most computers/laptops come preinstalled with Windows Home.
Also, I think it's misleading to say no VM is needed, it's just more transparent now.
Servers usually need neither of them, though.
Docker on WS 2016 is Windows containers only, this is for linux containers on a windows system.
* https://github.com/docker/labs/blob/master/windows/windows-c... * https://docs.docker.com/docker-for-windows/release-notes/#/b...
> Containers and images created with Docker for Windows are shared between all user accounts on machines where it is installed. This is because all Windows accounts will use the same VM to build and run containers. In the future, Docker for Windows will better isolate user content.
Can someone change the title?
Now available for windows! :D
On the bright side. Maybe that will make finding the perfect combination (i.e. one that doesn't crash) of OS + kernel + docker version + filesystem easier because there is limited diversity on Windows.
