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

Vagrant Share

vagrantup.com

Post reply on HN
Print view View original

31–40 of 47 posts

Re: Vagrant Share

#31

Post by makmanalp »

bhouston wrote: post #6

Sort of neat. We already share our vagrants within our office as we port forward from the host computers to the guest. Thus to access bob's vagrant I just go http://bob-computer:3120/ , etc... We use this feature periodically and it is useful in those cases. I guess this new feature is mostly for remote collaborations where you are not in the same secure network. PS. Vagrant is one of the most reliable parts of our h…

I know this isn't the right place for it but here we go: it's a total PITA when somehow the VM connection gets severed and "vagrant ssh" won't work and "vagrant shutdown" won't shutdown cleanly, so you have to kill it by hand and then reboot MANUALLY in virtualbox because the VM gets stuck in the grub menu after a non-clean kill. So then you have to wait for it to boot completely, then shut down normally and then run vagrant up again.

That connection dies for me periodically, like a few times a week. Anyone manage to solve that one?

Re: Vagrant Share

#32

Post by kayoone »

makmanalp wrote: post #31
bhouston wrote: post #6

Sort of neat. We already share our vagrants within our office as we port forward from the host computers to the guest. Thus to access bob's vagrant I just go http://bob-computer:3120/ , etc... We use this feature periodically and it is useful in those cases. I guess this new feature is mostly for remote collaborations where you are not in the same secure network. PS. Vagrant is one of the most reliable parts of our h…

I know this isn't the right place for it but here we go: it's a total PITA when somehow the VM connection gets severed and "vagrant ssh" won't work and "vagrant shutdown" won't shutdown cleanly, so you have to kill it by hand and then reboot MANUALLY in virtualbox because the VM gets stuck in the grub menu after a non-clean kill. So then you have to wait for it to boot completely, then shut down normally and then run…

If i somehow can't connect to the VM anymore "vagrant halt" followed by "vagrant up" usually fixes that. Doesn't happen alot though.

Re: Vagrant Share

#33

Post by makmanalp »

kayoone wrote: post #32
makmanalp wrote: post #31

Earlier quoted context omitted.

I know this isn't the right place for it but here we go: it's a total PITA when somehow the VM connection gets severed and "vagrant ssh" won't work and "vagrant shutdown" won't shutdown cleanly, so you have to kill it by hand and then reboot MANUALLY in virtualbox because the VM gets stuck in the grub menu after a non-clean kill. So then you have to wait for it to boot completely, then shut down normally and then run…

If i somehow can't connect to the VM anymore "vagrant halt" followed by "vagrant up" usually fixes that. Doesn't happen alot though.

Halt breaks too, though!

Re: Vagrant Share

#34

Post by kayoone »

This is great! What i am still missing is sharing a vagrant vm across multiple machines i work with easily. Basically to set this up i have to set up a base box and bring that up on another machine and then manually switch the hd uids so that they are in sync. Otherwise dropbox sharing my vagrant workspace will sync a different id and on the other pc vagrant up wont find the existing vm and start a new one.

Also when i install a new service inside the vm on one machine, i have to repackage the vm and reinit it on the other machines later.

Kind of a pita, has anyone an elegant way to solve this ? Can't believe no one is working with multiple machines at work/home.

Re: Vagrant Share

#35

Post by kayoone »

makmanalp wrote: post #33
kayoone wrote: post #32

Earlier quoted context omitted.

If i somehow can't connect to the VM anymore "vagrant halt" followed by "vagrant up" usually fixes that. Doesn't happen alot though.

Halt breaks too, though!

Strange, question might be why your ssh connection breaks down like that. I get disconnected when i put my machine to sleep but after waking up i can just vagrant ssh back into it.

Re: Vagrant Share

#36

Post by iaskwhy »

bhouston wrote: post #7
iaskwhy wrote: post #5

Earlier quoted context omitted.

Well, this came to my mind because I'm developing a new responsive web app and wanted to test it on both my iPhone and iPad. There are several ways around this but I guess this makes it so much easier. Also, as noted, seems great to let your colleagues see what's going on with your work.

> I'm developing a new responsive web app and wanted to test it on both my iPhone and iPad. This is already easily done just by configuring port forwarding from your host to your guest in your vagrantfile. e.g.: config.vm.network :forwarded_port, host: 8080, guest: 80

I'm not sure that's the way to do it. I mean, I do use forwarded ports on my projects and I also configure my private network for each one but at least on my current machine it doesn't allow outside access unless I mess with the router and the firewall. A little bit easier would be to configure a network as "public_network" on the Vagrantfile. I assume this works for most people but, again, my machine doesn't vagrant up if I have a public_network configured. I never tried to figure out why, it's not something I had to care about that much to be honest.

So, as you can see, if vagrant share works as announced it would make it much easier for me for that particular task.

Re: Vagrant Share

#37

Post by kayoone »

IgorPartola wrote: post #23

This is exactly why widespread adoption of IPv6 would make everyone more productive. Why doesn't every Vagrant box have an IPv6 address that you can expose by opening up firewall rules? Well, aside from ISP's being slow and developers not spending the 40 minutes necessary to set IPA tunnel, VirtualBox does not support IPv6 addresses on bridged interfaces if the host interface is a wireless card. Sad day all around. E…

Why? Even now, you can just forward the guest port to the host and expose it to give people access.

Vagrant share makes the process of doing this super easy which is great, because you don't need to do any of that manual trickery.

Re: Vagrant Share

#38

Post by colinc »

makmanalp wrote: post #31
bhouston wrote: post #6

Sort of neat. We already share our vagrants within our office as we port forward from the host computers to the guest. Thus to access bob's vagrant I just go http://bob-computer:3120/ , etc... We use this feature periodically and it is useful in those cases. I guess this new feature is mostly for remote collaborations where you are not in the same secure network. PS. Vagrant is one of the most reliable parts of our h…

I know this isn't the right place for it but here we go: it's a total PITA when somehow the VM connection gets severed and "vagrant ssh" won't work and "vagrant shutdown" won't shutdown cleanly, so you have to kill it by hand and then reboot MANUALLY in virtualbox because the VM gets stuck in the grub menu after a non-clean kill. So then you have to wait for it to boot completely, then shut down normally and then run…

I ran into a similar (completely maddening) situation when using an Ubuntu 12.04 LTS guest with Vagrant configured to create a private network.

I don't recall the exact cause of the failure, but switching to the virtio networking drivers has completely solved this issue for me.

  config.vm.provider :virtualbox do |vb|
    vb.customize ['modifyvm', :id, '--nictype1', 'virtio']
  end

Re: Vagrant Share

#39

Post by nickstinemates »

fletchowns wrote: post #29
dchuk wrote: post #20

Earlier quoted context omitted.

You are vastly overestimating the technical abilities of the average QA person. "Just as easily spinning up their own VM with the Vagrantfile" assumes a significant base understanding of a lot of technologies.

I think you are vastly underestimating their abilities. You install git, virtual box, and vagrant. Clone the repo and type vagrant up. If they've never done it they can refer to the wiki page you typed up for everybody. I know every QA person at my workplace could easily do it.

I've found there's a broad categorization talent/skills in QA, but a lot of it boils down to this separation -> Able to do development related tasks (set up their own envs, run different versions of apps, etc.) or not.

Anecdotally, it also seems to correlate with how useful Developers usually find their peers.

Re: Vagrant Share

#40

Post by IgorPartola »

kayoone wrote: post #37
IgorPartola wrote: post #23

This is exactly why widespread adoption of IPv6 would make everyone more productive. Why doesn't every Vagrant box have an IPv6 address that you can expose by opening up firewall rules? Well, aside from ISP's being slow and developers not spending the 40 minutes necessary to set IPA tunnel, VirtualBox does not support IPv6 addresses on bridged interfaces if the host interface is a wireless card. Sad day all around. E…

Why? Even now, you can just forward the guest port to the host and expose it to give people access. Vagrant share makes the process of doing this super easy which is great, because you don't need to do any of that manual trickery.

Several reasons. First, you are likely behind a NAT. Sure, you can share your Vagrant box with people in your office, but you can't share them if you are working remotely. This has actually bitten me on my team (I work remotely) where I needed to debug a Puppet issue on a coworker's VM and had to try to ssh to his box. What a pain.

Second, port forwarding is fun and all, but why bother when you can do things properly and directly. Your host machine can still control everything and you won't need to do anything manual. All the manipulations that are required can still be hidden behind the simple `vagrant share` command. You can even combine this with a dynamic DNS entry so that you could share not just an IP address but a simple name.

Third, it would be less effort do support this, than to maintain yet another NAT traversal service.\

Fourth, this would speed up adoption of IPv6, something we will all benefit from in the long run.

Post reply on HN