Hacker News Reader

Comment by noir_lord | Hacker News Reader

> Cut the bullshit and just run Linux on the bare metal,

I run Linux on Linux via vagrant, it's not about my program running faster it's about isolating a client projects dependencies from each other so when I have to work on that system that is still in production on PHP Current-1 or Ruby-1 I don't have to fuck with my host OS at all.

In fact I have very few developer bits and bobs installed on the host (mostly just JetBrains stuff) and all the actual tooling is run in the VM, this makes for far easier deploys for myself since my process is

pull projectname/(site||name), pull projectname/vagrant, vagrant up.

It takes me less than 30 minutes from reinstalling to having half a dozen projects with all their weird dependencies and cruft installed and I never have to worry about breaking something else or needing to blow away a machine for some reason.

I'm happy to trade some performance for running damn near everything in a guest OS for that.

View on HN

Curious, why Vagrant and not Docker? Then you don't need to run a VM, but still get the same isolation.

well pointed!

I am guessing is that when he started working on this stuff docker was in it's infancy (still is IMHO), and had no reason/time to port it.

Or you could have glanced at the article and seen that your guess is wide off the mark.. ;-)

Which article?

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).

> Curious, why Vagrant and not Docker?

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.

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...

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.

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...

Reply on news.ycombinator.com