Comment by mstade | Hacker News Reader

Comment by mstade | Hacker News Reader

It's unfortunate that they announced Otto as the "successor to Vagrant" when in reality it seems Vagrant and Otto solve different, albeit related problems. Otto seems like it's solving the high level issues, to introduce a sort of hive-mind conformity; whereas Vagrant solves the issue of efficiently automating the creation of specific environments. It makes sense then that Otto uses Vagrant to achieve it's goal, but it's a bit confusing to call it a "successor" then. Vagrant is a great piece of tooling, and it's good to see that it lives on despite confusing messaging.

Just reading this announcement, it seems 1.8 is an amazing release. The linked clones by the sounds of it seems like it'll solve on of the major issues I've had with Vagrant. Additionally, this little nugget is hidden under minor features, but should really have a heading of its own:

> Vagrant now automatically installs VirtualBox for a smoother getting started experience on Mac OS X and Windows.

Awesome, kudos!

Agreed. For those who didn't read to the end of the post they tacked this on the end:

"Vagrant 1.8 is our first major Vagrant release since releasing Otto. There was a lot of concern around the future of Vagrant since announcing Otto as the "successor to Vagrant". Many of the features of Vagrant 1.8 are the result of Otto needing them to reach that goal. Vagrant 1.8 is an example of how Vagrant will continue to improve – in major ways – alongside Otto."

> Vagrant now automatically installs VirtualBox for a smoother getting started experience on Mac OS X and Windows.

Anyone know if it does this when VMWare is already installed?

Yes. It's a known issue that appears to be on the roadmap for 1.8.1: https://github.com/mitchellh/vagrant/issues/6708

You can call `vagrant up --no-install-provider` for the old behaviour. See also: https://docs.vagrantup.com/v2/cli/up.html

This is a dumb default for Windows users that use Hyper-V (like I do). You can't run Hyper-V and Virtualbox at the same time.

This is a dumb default for anyone on any platform that has a virtualisation tool already installed.

But then again, this is the person/organisation that defaults to a bash login shell during provisioningg (which in turn causes the famous "stdin: is not a tty" warning/error), just to avoid having to source some files in their default base box.

Reply on news.ycombinator.com