plus, tell us, the machine where this is failing OS? host is 64bit?
I have been reading that are some issues with some 32 bit boxes on 64 bit host, seems due how the were created, or how they are imported.. not sure yet.. On Thu, Mar 27, 2014 at 9:56 AM, Alvaro Miranda Aguilera <[email protected]>wrote: > Hello Jed, > > on the computer that is failing check the vagrant version (1.5.1), and try: > > vagrant box add chef/centos-5.10-i386 > > in the vagrantfile: > > remove this: > config.vm.box_url = "chef/centos-5.10-i386" > > and leave this: > config.vm.box = "chef/centos-5.10-i386" > > and should work. > > if fail, share the vagrantfile to have a look at. > > Alvaro. > > > > > > > On Thu, Mar 27, 2014 at 6:31 AM, Jed Herzog <[email protected]> wrote: > >> Hello, >> >> I have a vagrant project that I made using vagrant 1.5 and puppet >> provisioning. I worked on it until it was working great. I gave it to a >> coworker and she gets errors. Not sure what is different. Here is the >> scenario. >> >> In my Vagrantfile I have: >> >> config.vm.box = "centos64" >> config.vm.box_url = "chef/centos-5.10-i386" >> >> This causes no issues for me. She gets an error >> >> ==> default: Box 'centos64' could not be found. Attempting to find and >>> install... >>> default: Box Provider: virtualbox >>> default: Box Version: >= 0 >>> ==> default: Loading metadata for box 'chef/centos-5.10-i386' >>> default: URL: https://vagrantcloud.com/chef/centos-5.10-i386 >>> The box you're adding has a name different from the name you >>> requested. For boxes with metadata, you cannot override the name. >>> If you're adding a box using `vagrant box add`, don't specify >>> the `--name` parameter. If the box is being added via a Vagrantfile, >>> change the `config.vm.box` value to match the name below. >>> >>> Requested name: centos64 >>> Actual name: chef/centos-5.10-i386 >>> >> >> So, even though I don't need to do this, we adjust her vagrantFile as >> this error message requests: >> config.vm.box = "chef/centos-5.10-i386" >> config.vm.box_url = "chef/centos-5.10-i386" >> >> Now, vagrant proceeds but we get this error. >> >>> ==> default: Running provisioner: puppet... >>> The `puppet` binary appears not to be in the PATH of the guest. This >>> could be because the PATH is not properly setup or perhaps Puppet is not >>> installed on this guest. Puppet provisioning can not continue without >>> Puppet properly installed. >>> >> >> If I change my vagrantFile to the config.vm.box = "chef/centos-5.10-i386" >> I get this same error. I change it back to config.vm.box = "centos64" and >> everything is good. >> >> What's going on? Why does that box name cause her issues and not me? I >> feel the PATH issue is due to the change in this name. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Vagrant" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
