Live data from Hacker News

Vagrant 1.4

vagrantup.com

31–40 of 64 posts

Re: Vagrant 1.4

#31

I had hoped that their Docker support would be some magical mechanism that would treat Docker as a kind of VirtualBox. That is, instead of using VirtualBox to create VMs, they would use Docker to create containers. 'vagrant ssh' would then SSH directly into a container instead of the host VM. Sadly, their Docker support is just a provisioner. :( I can do that myself too in a shell script.

If that is what you want, then just install docker on your system ;-)

Re: Vagrant 1.4

#32

Earlier quoted context omitted.

Can you explain what Vagrant adds on top of VirtualBox? When I tried it it didn't seem that different than just using VirtualBox directly.

The biggest thing it adds on top of VirtualBox is a consistent workflow. If it helps, think of what Vagrant does technically as useless, and think of Vagrant only as a process discipline: to get a dev environment for any project you "vagrant up", to close it out "vagrant destroy", to access it "vagrant ssh", etc. As soon as you get this consistent workflow, then you can teach it to your entire organization and the wh…

Is this mostly appropriate for web development? Could it work for embedded or desktop development? Seems like it might be a lot of overhead if you only need to install an IDE and a compiler.

Presumably this is also mostly used with Linux. How do people manage Windows licenses with Vagrant?

Re: Vagrant 1.4

#33

I had hoped that their Docker support would be some magical mechanism that would treat Docker as a kind of VirtualBox. That is, instead of using VirtualBox to create VMs, they would use Docker to create containers. 'vagrant ssh' would then SSH directly into a container instead of the host VM. Sadly, their Docker support is just a provisioner. :( I can do that myself too in a shell script.

If that is what you want, then just install docker on your system ;-)

+1

To use docker on my mac I have replaced Vagrant with boot2docker (http://github.com/steeve/boot2docker). I didn't need all the moving parts anyway - the VM is always the same, the application-specific bits are all defined inside the containers.

Re: Vagrant 1.4

#34

I've just spent 5 minutes trying to learn what Vagrant is and how it works. The home page didn't help me with that AT ALL. It's full of vague terms like "development environment" and "work environment" and buzzwords claiming to "maximize productivity". In your About page, please describe the typical USAGE SCENARIOS of your software and how does it help in those cases exactly.

This is linked in the 2nd sentence in the getting started section that is linked from one of the two biggest call-to-actions on the homepage: http://docs.vagrantup.com/v2/why-vagrant/ I'm sorry you couldn't find that!

Thanks for yor work Mitchell. I use Vagrant everyday.

Re: Vagrant 1.4

#35
post #27
post #15

I like vagrant, but would love it to work with VMWare fusion, but cannot justify paying more than the cost of fusion for a vagrant plugin. Anyone aware of an open source alternative to the official VMWare provisioner?

Why is using Virtual Box not an option if you are price sensitive?

VirtualBox is getting better, but it's still no match for vmware's performance(especially file share).

Re: Vagrant 1.4

#36
post #33

Earlier quoted context omitted.

If that is what you want, then just install docker on your system ;-)

+1 To use docker on my mac I have replaced Vagrant with boot2docker ( http://github.com/steeve/boot2docker ). I didn't need all the moving parts anyway - the VM is always the same, the application-specific bits are all defined inside the containers.

how do you launch boot2docker on your mac, raw virtualbox? or do you mean you actually dual-boot to it?

Re: Vagrant 1.4

#37

Earlier quoted context omitted.

The biggest thing it adds on top of VirtualBox is a consistent workflow. If it helps, think of what Vagrant does technically as useless, and think of Vagrant only as a process discipline: to get a dev environment for any project you "vagrant up", to close it out "vagrant destroy", to access it "vagrant ssh", etc. As soon as you get this consistent workflow, then you can teach it to your entire organization and the wh…

Is this mostly appropriate for web development? Could it work for embedded or desktop development? Seems like it might be a lot of overhead if you only need to install an IDE and a compiler. Presumably this is also mostly used with Linux. How do people manage Windows licenses with Vagrant?

Is this mostly appropriate for web development? Could it work for embedded or desktop development?

No, it's very useful for desktop, and especially embedded development. It lets you have consistent images to test your code against.

Presumably this is also mostly used with Linux. How do people manage Windows licenses with Vagrant?

No, it's very popular on both Windows and OS-X. Virtualbox is most popular on both platforms (because it is free).

Re: Vagrant 1.4

#38
post #35
post #27

Earlier quoted context omitted.

Why is using Virtual Box not an option if you are price sensitive?

VirtualBox is getting better, but it's still no match for vmware's performance(especially file share).

I last time I used vagrant was 1.2 on whatever the latest virtualbox at the time was. The performance was about half as good as the host machine. The host machine was running the desktop version of Ubuntu at the time. I was not able to easily identify if VirtualBox's performance problems were CPU or IO bound. If I hear that the performance is close to native, I'll give it another try. Otherwise, I can't see the point.

Re: Vagrant 1.4

#39
post #37

Earlier quoted context omitted.

Is this mostly appropriate for web development? Could it work for embedded or desktop development? Seems like it might be a lot of overhead if you only need to install an IDE and a compiler. Presumably this is also mostly used with Linux. How do people manage Windows licenses with Vagrant?

Is this mostly appropriate for web development? Could it work for embedded or desktop development? No, it's very useful for desktop, and especially embedded development. It lets you have consistent images to test your code against. Presumably this is also mostly used with Linux. How do people manage Windows licenses with Vagrant? No, it's very popular on both Windows and OS-X. Virtualbox is most popular on both platf…

> it's very popular on both Windows and OS-X.

No, I think that they meant with Windows Guests (hence the license question).

I don't think that Vagrant is used much for coding Windows applications, but rather coding Linux (web) applications from Windows hosts.

I've never used it, but it looks like there is a way to use this for Windows Guests as well: http://www.thomasvjames.com/2013/09/create-a-windows-base-bo...

YMMV

Re: Vagrant 1.4

#40
post #35

Earlier quoted context omitted.

VirtualBox is getting better, but it's still no match for vmware's performance(especially file share).

I last time I used vagrant was 1.2 on whatever the latest virtualbox at the time was. The performance was about half as good as the host machine. The host machine was running the desktop version of Ubuntu at the time. I was not able to easily identify if VirtualBox's performance problems were CPU or IO bound. If I hear that the performance is close to native, I'll give it another try. Otherwise, I can't see the point…

If you are on Linux, why not use vagrant with lxc containers?
Post reply on HN