Docker is awesome, right? And thanks to boot2docker Windows users were no longer left out of the fun. Still, setting everything up could be a PITA and you had to install Oracle VirtualBox to use it as Docker containers were actually run inside of a VM (which was the purpose of boot2docker).
This short post is more of a note to myself for when I run into the same problem. I just wasted an hour on it so I guess that justifies it. So, what happened? I wanted to check out the new Docker Machine with Hyper-V support, but the Hyper-V Manager told me it could not connect to my local computer.
This blog is built with Hugo , which allows me to use some great CI tools like Wercker . The first part of writing a wercker.yml is picking a build container. A build container on Wercker is the environment in which your build or deploy steps run. Wercker used to build its own containers for that, but they’ve moved away from that approach to Docker containers.