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

41–50 of 120 posts

Re: Vagrant 2.0

#41

Post by neovive »

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…

Homestead is wonderful! I've been using it for years for Laravel development. Thanks!

Re: Vagrant 2.0

#42

Post by korzun »

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.

Re: Vagrant 2.0

#43

Post by spilk »

thrownhwn wrote: post #31
KZeillmann wrote: post #11

What's the use case where I'd want to use Vagrant instead of Docker?

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 me to use Hyper-V.

Re: Vagrant 2.0

#44

Post by sctb »

trapperkeeper74 wrote: post #37
orev wrote: post #20

Earlier quoted context omitted.

I guess the main thing you're missing is that it you're not obligated to comment on things that don't apply to you?

Snowflake SJW is triggered.

Please don't post like this here, it breaks the guidelines by being uncivil and unsubstantive.

https://news.ycombinator.com/newsguidelines.html

Re: Vagrant 2.0

#45

Post by yebyen »

thrownhwn wrote: post #31
KZeillmann wrote: post #11

What's the use case where I'd want to use Vagrant instead of Docker?

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.

I use Minikube with the VirtualBox driver, and it is the only way that I have been able to deal with my slightly unusual networking requirements and do local dev with Kubernetes.

VirtualBox lets you forward ports from within the VM to your localhost directly, bypassing iptables and any default routes.

Our network uses a "no-split-tunneling" VPN, so most of the Docker networking solutions are completely unusable for me.

Kubernetes fortunately provides easy ways to enumerate the services that you intended to expose (via ingress, or similar) so it's absolutely trivial to script forwarding every exposed service or ingress to the localhost IP. I still am editing /etc/hosts file if I ever need to use a host-based route, and I have some interesting issues with SSL certificates that sometimes did not have the server name that I expected on them, but for the most part this works great for me.

I am a Mac user and showed my coworker who is a Windows user, we tried to do the same thing on his machine and it was even easier because there is no notion of privileged ports below 1024. So, it works the same way but with one less workaround.

Re: Vagrant 2.0

#46

Post by justinhj »

choward wrote: post #12
Kiro wrote: post #10

How does Vagrant work with Docker? Why do you need Vagrant if you're using Docker?

Vagrant abstracts virtual machines. If you want to simulate multiple machines on the same computer you need VMs. You can have multiple docker containers running in those VMs that communicate across VMs. You can then deploy to real hardware having tested the communication across machines.

You can also run multiple docker-machine instances which can run on say VirtualBox. This is a how we have developers learn about and test Docker Swarm on a single machine. I've really run out of use cases for Vagrant at this point.

Re: Vagrant 2.0

#47

Post by tmzt »

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…

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.

Re: Vagrant 2.0

#48

Post by emddudley »

bdcravens wrote: post #39
orev wrote: post #20

Earlier quoted context omitted.

I guess the main thing you're missing is that it you're not obligated to comment on things that don't apply to you?

It seemed like a pretty legitimate question: is there a compelling reason to give Vagrant 2 a look if Docker/Kubernetes is your current workflow? It seems to me you took it as more of an us-vs-them comment.

You probably wouldn't look at Vagrant if you are using Docker/Kubernetes. Vagrant (virtual machines) and Docker (containers) fill different niches. If you can accomplish your work with containers then you don't need to manage virtual machines.

Re: Vagrant 2.0

#49

Post by SiVal »

mitchellh wrote: post #22
jimmar wrote: post #4

Just from the version number I thought there'd be a few major changes, but really it just seems like another point release that happens to increment the major version number. (Which is totally fine by me. I rely on Vagrant a lot and I'm glad the new version doesn't introduce breaking changes). Change log is here: https://github.com/mitchellh/vagrant/blob/v2.0.0/CHANGELOG.m...

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 think of 2.0.0 as the most-stable version of 1.x with 2.0.1 being the less-stable introduction of the great, new features.

Re: Vagrant 2.0

#50

Post by Blaine0002 »

neovive wrote: post #41
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…

Homestead is wonderful! I've been using it for years for Laravel development. Thanks!

He meant Drupal VM :)
Post reply on HN