Hacker News Reader

Comment by drinchev | Hacker News Reader

Was so sad, because vagrant stopped working on my colleague's computer after this update.

I had to force Vagrant to use the "system" ssh binary ( VAGRANT_PREFER_SYSTEM_BIN=1 ), since the internal vagrant OpenSSH stopped working.

And this is without WSL being in use.

It's already so complicated to run even git / vagrant on a windows machine, that I'm wondering how are people developing with it.

View on HN

> It's already so complicated to run even git / vagrant on a windows machine, that I'm wondering how are people developing with it.

I find Git fine, but the Vagrant/Virtualbox ecosystem...

I dread every Windows update because something will break the setup, and that will be a day lost to figuring out which version of every component I need in order for my Virtual Machines to boot/build.

I would pay money for something that "Just works". Wondering if VMWare rather than Virtualbox is that, but no way to test without spending money.

Run the vagrant inside Debian (possibly inside virtual box/hyperv/VMware/parallels running on your host OS).

Debian doesn’t pull or push the proverbial update rug under your legs without asking, and things rarely if ever break on a Debian stable update.

Run VMs in Hyper-V. That just works

My vagrant install failed under HyperV after the update. After spending a couple of hours trying to get it working again I switched over to Docker for some legacy Rails projects and installed native binaries for the Elixir project I was working on. I’ve used Vagrant for years but I guess it was time to move on.

I could find many ways to describe HyperV, but "just works" would definitely not be a phrase I'd use.

In comparison with VirtualBox, Hyper-V “just works”

Reply on news.ycombinator.com