I have been using Docker for Windows on a Windows 10 64-bit machine and it has worked really well for me.
However, in my case, I have a pretty beefy Windows 10 64-bit development server which I use to run several development VMs. Development takes place on a weaker laptop which interacts with the VMs over the network.
Previously, I had a Ubuntu VM running the latest version of docker with bridged network enable. Effectively, that makes the VM look like a separate machine on my network with its own IP address to avoid port collisions with the other VMs.
With Docker for Windows, this does not seem to be possible (yet). I added an “external” hyper-v network, and added an extra network adapter to the MobyLinuxVM machine and connected it to the external network. However, when I attempt to start Docker for Windows, it does not start or shutdown properly and I have to force the machine to shutdown.
It would be nice if the Docker for Windows networking settings allows us to run the MobyLinuxVM in “bridged (VirtualBox term)” / “external (hyper-v terms)” mode.