News for hackers. Stuff that matters.

A comment on Vagrant 2.0. Parent comment

Re:Vagrant 2.0 by spilk on Thursday September 07, 2017 @04:13PM (#15195274)
The whole Hyper-V thing with the default Docker for Windows stuff has put me off - is there a workaround to go back to using a VirtualBox VM again? I do a fair amount of development on Windows machines along with Mac/Linux so I need something that works consistently among all those platforms.

Vagrant is filling the void for some of those projects since it just works with no fuss on Mac/Windows/Linux without forcing me to use Hyper-V.

[ Parent | on HN ]
Re:Vagrant 2.0 by yebyen on Thursday September 07, 2017 @04:26PM (#15195385)
Absolutely, you can boot your preferred distribution for running Docker on[1] (using Vagrant even! setting the provider to VirtualBox), forward the port that Docker is running on (2376?) to your physical host/localhost[2], and set a few variables on the client machine to get your docker client talking to that ("remote") docker daemon[3]

[1]: https://coreos.com/os/docs/latest/booting-on-vagrant.html

[2]: https://www.vagrantup.com/docs/networking/forwarded_ports.ht...

[3]: https://docs.docker.com/machine/reference/env/

Or, as tmzt mentioned, minikube and minishift will also let you set --vm-driver=virtualbox on start. Those are nice even if you don't want to use Kubernetes (but there are plenty of options.)

[ Parent | on HN ]
Re:Vagrant 2.0 by tmzt on Thursday September 07, 2017 @04:23PM (#15195365)
You can still run Docker Machine (part of the old Toolbox) for VirtualBox support. minikube/minishift can also be used as docker VMs and download up to date iso images automatically.
[ Parent | on HN ]