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

101–110 of 120 posts

Re: Vagrant 2.0

#101

Post by allover »

ubernostrum wrote: post #89
hallman76 wrote: post #87

Earlier quoted context omitted.

you, and they, were doing it wrong. The point of vagrant is that you type 'vagrant up' and you have a working environment. All of my projects use vagrant to ensure compatibility. You can 'git clone' and 'vagrant up' and have a working environment as soon as the provisioning task completes.

Thanks for the help. I trust that the people who provided whatever configuration it used knew what they were doing, but it was still incredibly flaky.

> I trust that the people who provided whatever configuration it used knew what they were doing

You should never trust that people know what they are doing in this industry.

Re: Vagrant 2.0

#102

Post by scaryclam »

ubernostrum wrote: post #89
hallman76 wrote: post #87

Earlier quoted context omitted.

you, and they, were doing it wrong. The point of vagrant is that you type 'vagrant up' and you have a working environment. All of my projects use vagrant to ensure compatibility. You can 'git clone' and 'vagrant up' and have a working environment as soon as the provisioning task completes.

Thanks for the help. I trust that the people who provided whatever configuration it used knew what they were doing, but it was still incredibly flaky.

I don't think I've ever encountered a Vagrant setup that was flaky and wasn't just down to the Devs not actually understanding how to write a vagrantfile. In my experience, those who have hate for vagrant are folks who either didn't know how to use it, or were burned by others who didn't. It's a real shame as well, vagrant's a really good tool.

Re: Vagrant 2.0

#103

Post by scaryclam »

jjoonathan wrote: post #92
hallman76 wrote: post #87

Earlier quoted context omitted.

you, and they, were doing it wrong. The point of vagrant is that you type 'vagrant up' and you have a working environment. All of my projects use vagrant to ensure compatibility. You can 'git clone' and 'vagrant up' and have a working environment as soon as the provisioning task completes.

Not my experience. Vagrant encounter 1: it would always exit immediately after barfing some garbage that messed up the line discipline. It wouldn't even print help menus. Reinstalling, 32 vs 64 bit, slightly different binary versions etc didn't seem to affect this behavior. Vagrant encounter 2: on a nearly virgin Windows box, "vagrant up" on a bog standard centos image stalled out for an entire work day. No stdout, n…

That screams badly written vagrant file to me.

Re: Vagrant 2.0

#104

Post by bboreham »

mateuszf wrote: post #19
wuunderbar wrote: post #15

Earlier quoted context omitted.

Vagrant lets you provision in a codified manner full-fledge VMs. This code can be pulled down by your developers to deploy a development environment on their machines. Inside of this you can choose to run containers of your apps with proper tooling built around it.

Can't you do the same thing with docker, docker compose?

The equivalent tool is docker-machine, not docker compose.

Though they de-emphasised that tool in favour of Docker for Mac and Docker for Windows which interact directly with the platform hypervisor to create a Linux VM.

Re: Vagrant 2.0

#105

Post by trengrj »

marcosscriven wrote: post #63

There are still times I look to Vagrant instead of, and alongside, Docker. The reason being Docker for Mac uses a VM anyway (an xhvye machine) - it does try to hide/abstract this away, but inevitably this leaks. The xhyve VM has the usual parameters memory, diskspace, CPUs, and not least a kernel. There are limited options to fiddle with these parameters, though you can log into it and poke around there. I thus find…

Yeah agreed. I just wasted 2 hours this week compacting my qcow2 docker image for my mac (by filling it with zeros). It was totally unintuitive that deleting images didn't free disk space.

Re: Vagrant 2.0

#106

Post by porker »

TwelveNights wrote: post #86
aidenn0 wrote: post #69

Earlier quoted context omitted.

Also the early reliance on virtualbox was a performance issue for some build environments even once they were up. I have at least one C++ project that (for windows) takes 8x as long to build on vbox vs. a real machine.

Wow, it doesn't rely on VirtualBox anymore? I remember using it before for the development environment of an old company, and that being a small nuisance. Nowadays, Docker is really miles ahead in terms of usage in development environments. Vagrant was pretty easy to set-up and use back then, but now Docker is much, much easier.

I need to get into this Docker malarkey for dev machines.

Running on Windows, how do you share files between the Docker image and the host machine? With Vagrant I use NFS.

Re: Vagrant 2.0

#107

Post by erikb »

Goopplesoft wrote: post #27
erikb wrote: post #26

Not to pull down the emotions here, but if the whole blog post is not saying more than "Hashicorp Vagrant 2.0" I doubt that there will be some meaningful content in that version. Was Vagrant bought by Hashicorp or something? Why not announce that?

It is owned by Hashicorp. Hashicorp was a company built around Vagrant initially.

I see, then I don't understand this blog post at all. Is my expectation weird that an anouncement blog post for a major version +1 should contain some features? Or have I just missed that part in the article?

Re: Vagrant 2.0

#108

Post by perbu »

aidenn0 wrote: post #69
ArlenBales wrote: post #55

Earlier quoted context omitted.

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

Also the early reliance on virtualbox was a performance issue for some build environments even once they were up. I have at least one C++ project that (for windows) takes 8x as long to build on vbox vs. a real machine.

I've just started using vagrant with vmware fusion. Whilst not cheap the fans on my computer are much happier these days.

Re: Vagrant 2.0

#109

Post by scaryclam »

marcosscriven wrote: post #63

There are still times I look to Vagrant instead of, and alongside, Docker. The reason being Docker for Mac uses a VM anyway (an xhvye machine) - it does try to hide/abstract this away, but inevitably this leaks. The xhyve VM has the usual parameters memory, diskspace, CPUs, and not least a kernel. There are limited options to fiddle with these parameters, though you can log into it and poke around there. I thus find…

I use linux, and while I use docker-compose for running many services together, I rarely bother with it for other work. It can misbehave pretty badly and making changes can mean long build times, so I still keep a surprising amount of stuff on vagrant setups.

Re: Vagrant 2.0

#110

Post by valfadeev »

jitl wrote: post #18
Kiro wrote: post #10

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

Vagrant is useful if you want to simulate a whole box, or a cluster of boxes - for example, you can spin up a cluster of 3 VMs to run Mesosphere DC/OS [0]. If you build and deploy just containers, and don't have any full VMs in your stack, then you might not need Vagrant. Vagrant also claims to provide a "good workflow for writing Dockerfiles"; it can provide a nicer user abstraction over `docker [many, many args]` f…

This is exactly where I began getting the most out of Vagrant, that is, simulating a distributed cluster locally. It gets me as close as possible to how it would work on the provider infrastructure, e.g. AWS. In particular, spinning up an automated Consul cluster and then using it get a group of RabbitMQ nodes to converge[0]. The same is certainly achievable through container orchestration, but that adds more layers of abstraction, especially on the networking side.

[0]: https://github.com/ValFadeev/consul-demo

Post reply on HN