Not the person you asked, but I use Vagrant because I deploy to hosts that I consider disposable and don't trust Docker in production, for reasons more thoroughly explained by the person that wrote this article: https://thehftguy.com/2016/11/01/docker-in-production-an-his...
Absolutely this, vagrant has bee reliable, stable (barring the odd oops on a new release) and fits my workflow, docker is interesting but the switching cost to payback ratio isn't there (yet, I'd really like to get rid of having to use NFS, that's accounted for 80% of my vagrant issues).
I have a Vagrant/Virtualbox workflow (on Windows host, so Docker not a great option yet) but curious: does Docker have shared folder support - via NFS or other?
It's been the getting stuff into & out of the VM that's most painful IMO.
On Windows, if you are using Docker Toolbox, you can keep using VirtualBox. The corresponding driver of docker-machine will spin up the VM that runs the docker daemon, which, once it's running, you can control from the "outside". It uses shared folders support to map the user's home directory by default: https://docs.docker.com/machine/drivers/virtualbox/
> On Windows, if you are using Docker Toolbox, you can keep using VirtualBox.
Oh awesome, thanks! I looked when Docker for Windows came out and (thankfully) spotted the "After Hyper-V is enabled, VirtualBox will no longer work" (?!) warning before trying it. I didn't dig any deeper.
Docker has better than just shared folder support, you can share folders, UNIX SOCKETS!!!, and DEVICES!!!!! And no need for NFS either, its just a bindmount into the container...
