> use it easily without first telling you to get complex, fragile external tooling like vagrant or virtualbox working. I won't get into virtualbox. But I haven

> use it easily without first telling you to get complex, fragile external tooling like vagrant or virtualbox working. I won't get into virtualbox. But I haven't found vagrant very fragile at all since Mitchell moved to omnibus (quite a while back). Most of the issues I had with vagrant were directly related to virtualbox, not vagrant itself. > Docker has a huge interest in making it easy for the legions of Mac-toting developers Well, sort of. They have a product that is inherently linux based. Getting a nice setup working on OS X is pretty trivial, takes a developer maybe a couple of hours one time to have something working.If they use someone else's solution, it takes minutes. Here's an ansible task I use to configure an ubuntu machine[1]. It's all of 24 lines. If you're running it against a VM, you just forward the 2375 port to your host. Then the workflow looks like: vagrant up docker build -t jkyle/awesomeness . Course you can get fancier. Ansible can pull down docker projects using git, build, and run them for you as well. [1] https://gist.github.com/jameskyle/b8e573d63da4dbaaf31a https://gist.github.com/jameskyle/b8e573d63da4dbaaf31a