-
Notifications
You must be signed in to change notification settings - Fork 111
Unable to up with vagrant-cachier installed on OSX #86
Comments
This occurs even when setting |
I seemed to have worked around it temporarily by setting |
@colindean this is weird.... I don't know why but somehow it seems that the box object is not set for the VM as the stacktrace points us to this line Just to double check, did you download the box before using the plugin? |
Yes, I downloaded the box before installing the plugin. Fabio Rehm [email protected] wrote:
|
It seems to me like the bug is caused by My guess is, L36 should be: I hit a similar issue using dvm:
|
I'm probably wrong in my assessment of the cause above. Further looking,
I think in this case, the 'machine.box.name' would be 'boot2docker-0.5.4.1' and that L36 as referenced above is really trying to pull that out to segregate all the caches by machine type. This makes sense, I'd want all centos-6 systems to share the same cache. We might want to
|
@miah thanks for all the info but I'm still trying to understand why the are you or @colindean able to share a full |
I just set everything up today on a new machine (latest Vagrant, VirtualBox, all the plugins, etc.) and didn't have a problem with the same |
I'll see if I can reproduce it with that option off. I'm afraid I can't post the |
I don't have a OSX machine around to try to reproduce this and trying to track it down without a Vagrantfile and a debug log is pretty hard. For now I'm going to close the issue and we can always get back to it when we have more information :-) |
I believe this is caused by the box that your Vagrant file previously referenced has been deleted. |
Is it worth re-opening this @fgrehm? We see this error pretty regularly. Try deleting your vagrant box and then vagrant reload a machine that used that box. |
FWIW, a vagrant destroy / vagrant up solves the problem |
I'll give it a try when I have a chance, lemme reopen |
Confirmed that I'm seeing the same issue on OS X after deleting a box and |
This was fixed in git, a new release will come out with it as soon as I'm done with the stuff tagged with the v1.0.0 milestone Thanks everyone for the information provided 😄 |
Unfortunately, I'm working on a confidential project, so I can't post the full Vagrantfile. Here are the relevant sections:
OSX 10.8.5. Virtualbox 4.2.18 (I guess I should update that, haha, but I don't think it's related because this config is working on a Linux machine with a version older than that).
Just installed Vagrant 1.4.3 and the plugins today. I had previously installed Vagrant 1.3.5.
The text was updated successfully, but these errors were encountered: