Another thing to consider would be the best practices as far as it's implementation in Hyper-V goes, the best use case for NIC teaming would be a Active/Standby connection mode. You can find more details about it here - http://insidevirtualization.com/windows-server-2012-r2/windows-server-2012-r2-nic-teaming-options/

@dashrender

This is actually a great article! It simplifies the procedure of installing a Hyper-V role from a GUI free Windows 2016 Core setup.

Have you seen this - https://www.server-world.info/en/note?os=Fedora_25&p=desktop&f=6 guide by any chance? Looks liek they managed to get it working.

Have you tried the fix from this page - http://www.microsoftfixit.eu/fix-0xc03a0014/ ?

Please mention another reason for not using Docker with Linux based operating systems:
If the UID on your host system doesn’t match the UID of the user inside your Docker container, you will have file ownership issues.

I think most people don’t encounter this because they are probably the only user on their development machine, and most people only add a single user in their Dockerfile to run their app.

I’m not sure about other Linuxes, but Ubuntu will assign the first user a UID of 1000 so if you’re the first user on an Ubuntu host and you have an Ubuntu-based Docker image, you won’t even notice.

Personally, i was given advice to avoid host volumes even though the case can be resolved with bindfs and a privileged machine in a Windows environment.