Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vagrant 2.0

hashicorp.com

Post reply on HN
Print view View original

51–60 of 120 posts

Re: Vagrant 2.0

#51

Post by yebyen »

spilk wrote: post #43
thrownhwn wrote: post #31

Earlier quoted context omitted.

Docker is a fragmented mess network wise if you need to support developers on both windows and macOS. Also, docker requires hyper-v and admin privs on Windows. And you can't run VirtualBox with hyper-v active so you need to choose either of the two options. Granted, you could run Docker in virtualbox but it wouldn't be very clean.

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 m…

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

Re: Vagrant 2.0

#53

Post by porkloin »

geerlingguy wrote: post #29

Since many people are still not too familiar with Vagrant (it doesn't seem to have the cachet of Docker for local dev environments), here are a few example Vagrant configurations that I use to build different servers for local testing/debugging: https://github.com/geerlingguy/ansible-vagrant-examples There are plenty of other great examples of Vagrant usage around the web, too, from Laravel's Homestead to (disclosure…

Thanks for all your hard work on DrupalVM, Jeff :)

Re: Vagrant 2.0

#55

Post by ArlenBales »

geerlingguy wrote: post #29

Since many people are still not too familiar with Vagrant (it doesn't seem to have the cachet of Docker for local dev environments), here are a few example Vagrant configurations that I use to build different servers for local testing/debugging: https://github.com/geerlingguy/ansible-vagrant-examples There are plenty of other great examples of Vagrant usage around the web, too, from Laravel's Homestead to (disclosure…

> Since many people are still not too familiar with Vagrant (it doesn't seem to have the cachet of Docker for local dev environments)

That's only a recent trend. Up until Docker became the standard a couple years ago (or whenever Docker for Mac was made stable), Vagrant was the standard for dev environments. The primary reason Docker succeeded Vagrant for dev environments is speed. Docker can have my dev environment up from scratch in seconds, but with Vagrant it took minutes.

Re: Vagrant 2.0

#57

Post by raziel2p »

sciurus wrote: post #2

Does the major version bump signify any major changes? The blog post and changelog don't seem to describe any.

Only one backwards incompatible change in the changelog. I think they just went the wordpress route and didn't want to bump from 1.9 to 1.10.

Re: Vagrant 2.0

#58

Post by dmix »

Does anyone find Vagrant useful for personal projects? Or is it only useful for team settings?

Re: Vagrant 2.0

#59

Post by sslalready »

korzun wrote: post #42
thrownhwn wrote: post #30

Anybody know if they has code-signed their Windows and macOS binaries with 2.0? It's a shame so many "core" developer tools are not code-signed. It makes life hard in companies where binary whitelisting is used.

> It makes life hard in companies where binary whitelisting is used. The application would still have to be audited, signed or not, prior to whitelisting.

In practise it's much easier to just trust well-known developers by whitelisting their code-signing certificates.

You could still get owned, of course, but the benefit here is that you're excluding everything not explicitly whitelisted, including drive-by downloads, crap on portable devices or random programs downloaded off the internet that someone thinks will solve their problem of the day.

When people do not code-sign their software every software update is painful. At work, where we run https://github.com/google/santa, it frequently happens that companies with code-signed software forget to code-sign their auto-updater, or random binaries that run during installation. Most of the time the application crashes/hang during the update (because some piece weren't allowed to run), only to remind to you update the software again when you restart the application.

Re: Vagrant 2.0

#60

Post by anonymousDan »

SiVal wrote: post #49
mitchellh wrote: post #22

Earlier quoted context omitted.

Its a focus on stability and we don't want you to be thinking about Vagrant either when you upgrade. We just want it to work. :) However, I want to be clear its not a marketing tactic in any way (re: hosh below, with an excellent comment!). It ends up being that implicitly but we waited and developed Vagrant 1.x for 5 years prior to calling it a 2.0 because we had a lot of goals we wanted to achieve: multi-provider,…

The actual nature of the product itself is what ultimately matters, of course, and I hear your's is outstanding, so good work. It's a less-important issue and just a convention, not a law, but normally v1.36.12 tells me "focused on stability and just working--boring but rock-solid", while 2.0.0 tells me "first release of great, new features--amazing but don't put too much weight on it yet". I wouldn't ordinarily thin…

I would think the opposite can often be the case. Usually a major version is where you get to remove a load of unused features since you can make breaking changes.
Post reply on HN