[vagrant-up] Ruby 2 Keyword Arguments in Vagrant

I'm using Vagrant version 1.6.5, and when I was trying to add a function to my vagrant file that use keyword arguments I got a syntax error. I ended up just adding a simple function to see if I got the same error and I did. So in my test I added: def bugbear(a:, b:) print #{a}

Re: [vagrant-up] Re: Shared Folders used by Chef Zero not being re-mounted after initial up

Hi Joe, guess it's this issue here: https://github.com/mitchellh/vagrant/issues/5199 Workaround is described in the issue HTH, Torben On Tue, Feb 10, 2015 at 10:35 PM, Joe George joegeorg...@gmail.com wrote: Running vagrant reload with --debug shows the following DEBUG messages DEBUG

[vagrant-up] Re: Rsync during provision process

I have solved the issue by writing a custom plugin. Right now it is very dirty, but it works for me. Hopefully someone can help clean up the code. https://github.com/jtnw/vagrant-force-rsync On Friday, February 6, 2015 at 1:14:58 PM UTC-5, Justin Beaty wrote: Hello, My vagrantfile uses

[vagrant-up] Shared Folders used by Chef Zero not being re-mounted after initial up

I have a multi node configuration that has been working for awhile. Something changed recently that has causing the failure. Setup: Vagrant 1.7.2 OSX Host VM Fusion 6 (with vagrant-vmware plugin) Ubuntu 14.04 Guests Chef 12 ChefDK 0.4.0 Provisioner: chef_zero My chef cookbooks are installed to

Re: [vagrant-up] Set VM name with hyperv provider

Also, ensure you are in the latest version.. vagrant version :) On Tue, Feb 10, 2015 at 10:09 PM, Alvaro Miranda Aguilera kiki...@gmail.com wrote: Nicola, always share the full vagrantfile please.. On Tue, Feb 10, 2015 at 9:51 PM, Nicola nickwor...@gmail.com wrote: Hello Alvaro, I try to

Re: [vagrant-up] Set VM name with hyperv provider

Nicola, always share the full vagrantfile please.. On Tue, Feb 10, 2015 at 9:51 PM, Nicola nickwor...@gmail.com wrote: Hello Alvaro, I try to do like your example bit I've this error: There are errors in the configuration of this machine. Please fix the following errors and try again:

Re: [vagrant-up] Ruby 2 Keyword Arguments in Vagrant

snip If you upgrade to 1.7, I believe you'll get keyword args. You can check the Ruby version by running: /opt/vagrant/embedded/bin/rubv -v (for Vagrant 1.7+) /Applications/vagrant/embedded/bin/ruby -v (for Vagrant 1.7) It appears it is still using 2.0.0: $

[vagrant-up] Rebunlding an upstream Vagrant Box?

All, I'm trying to rebundle the Ubuntu vagrant box (add some stuff to it). So, I started with the virtualbox-ovf builder. I have a resulting output-virtualbox-ovf/ directory with the following files in it. [chef=dev] Douglass-MacBook-Pro:output-virtualbox-ovf doug$ ls -l total 819680

[vagrant-up] Re: Shared Folders used by Chef Zero not being re-mounted after initial up

Running vagrant reload with --debug shows the following DEBUG messages DEBUG chef_zero: Not sharing /fuse/vendor/cookbooks, exists as /tmp/vagrant-chef/f08a2718cb37f3752d8907ba1ab2/cookbooks DEBUG chef_zero: Not sharing /fuse/source/cookbooks, exists as

Re: [vagrant-up] Rebunlding an upstream Vagrant Box?

Ronan, Thanks. So, you know, I thought maybe I could take my original config that generates an EC2 AMI, and just put a vagrant post processor at the end of that, and voila, I'd have an EC2 AMI and a vagrant box built from the same source. Simple, right? Well, I tried that, and I'm getting The

Re: [vagrant-up] Rebunlding an upstream Vagrant Box?

Alvaro. I guess I meant to post to the packer list. Oops. Anyway, option B is what I am doing. I have a resultant ovf file. What I can't find anywhere, is how do I then convert that to a .box file so that vagrant can use it? Doug. On Tuesday, February 10, 2015 at 12:51:27 PM UTC-8, Alvaro

Re: [vagrant-up] Cannot up a Vagrant machine

Hello, can you provide the Vagrantfile generated, confirm what command are you using.. I assume vagrant up also, run the command like this VAGRANT_LOG=debug vagrant up | tee vagrant_up.log and share a link to a gist or pastebin for that log Thanks On Wed, Feb 11, 2015 at 6:26 AM, shay

Re: [vagrant-up] Rebunlding an upstream Vagrant Box?

Hi Douglas, Maybe you can use Packer's Vagrant post-processor? https://www.packer.io/docs/post-processors/vagrant.html Regards, Ronan Amicel On Tue, Feb 10, 2015 at 10:12 PM, Douglas Garstang doug.garst...@gmail.com wrote: Alvaro. I guess I meant to post to the packer list. Oops. Anyway,

Re: [vagrant-up] Rebunlding an upstream Vagrant Box?

Hello, 2 options. A. you create a box using the source machine you provision with the Vagrantfile, then you need to use vagrant package https://docs.vagrantup.com/v2/cli/package.html It need to match the name of the vm in the gui, so you can use VBoxManage list vms and then vagrant

Re: [vagrant-up] Ruby 2 Keyword Arguments in Vagrant

Hey there, Vagrant uses its own embedded Ruby. I believe 1.6.5 runs Ruby 2.0 which supports keyword args, but not required ones. This should work: def bugbear(a: nil, b: nil) # ... end If you upgrade to 1.7, I believe you'll get keyword args. You can check the Ruby version by

Re: [vagrant-up] Set VM name with hyperv provider

I'm on the latest release of Vagrant (1.7.2) and seems that configuration is not supported... Il giorno martedì 10 febbraio 2015 10:11:29 UTC+1, Alvaro Miranda Aguilera ha scritto: Also, ensure you are in the latest version.. vagrant version :) On Tue, Feb 10, 2015 at 10:09 PM,