News for hackers. Stuff that matters.

A comment on Vagrant 2.0. Parent comment

Re:Vagrant 2.0 by TwelveNights on Thursday September 07, 2017 @11:08PM (#15197638)
Wow, it doesn't rely on VirtualBox anymore? I remember using it before for the development environment of an old company, and that being a small nuisance.

Nowadays, Docker is really miles ahead in terms of usage in development environments. Vagrant was pretty easy to set-up and use back then, but now Docker is much, much easier.

[ Parent | on HN ]
Re:Vagrant 2.0 by aidenn0 on Friday September 08, 2017 @03:35PM (#15203309)
Vagrant calls the backends "providers." It ships with 4 providers IIRC (VirtualBox, Hyper-V, VMWare, Docker), and there are plugins for dozens of others (it's so large a list because there's one provider each for pretty much every cloud service out there, even ones I've never heard of).

I think that VirtualBox and VMWare are the only two providers that work everywhere, unless docker runs on windows now.

[ Parent | on HN ]
Re:Vagrant 2.0 by porker on Friday September 08, 2017 @04:15AM (#15198667)
I need to get into this Docker malarkey for dev machines.

Running on Windows, how do you share files between the Docker image and the host machine? With Vagrant I use NFS.

[ Parent | on HN ]
Re:Vagrant 2.0 by TwelveNights on Wednesday September 13, 2017 @09:11PM (#15244213)
To expand on the other commentor, check out volumes: https://docs.docker.com/engine/admin/volumes/volumes/.
[ Parent | on HN ]
Re:Vagrant 2.0 by h_r on Monday September 11, 2017 @07:43PM (#15223492)
You basically create a mount point inside the VM to a place on your host disk.
[ Parent | on HN ]