-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vagrant up failing after upgrade: The box boxname
could not be found.
#1624
Comments
OK, my existing I'm going to try I remember reading in another issue that the new box format is different, and maybe that is burning me. If the new |
Works with a fresh box, so it's something in the old boxes. Time to fire up DiffMerge. |
Ah. The new format drops boxes under the {"provider":"virtualbox"} So the entirety of my fix was cd ~/.vagrant.d/boxname
mkdir virtualbox
mv box-disk1.vmdk box.ovf Vagrantfile virtualbox
cd ../working-box
cp virtualbox/metadata.json ../boxname/virtualbox Some plugin woes to sort out, but that's another topic. Blog post time (once I confirm this isn't detailed in some Really Obvious Spot). |
Good workaround, validated 6/4/2013, Vagrant 1.2.2 |
Yeah, there's a comment on that post that is even easier ( |
Thanks for the post. Changing into new folder structure helped me as well. |
I went from Vagrant 1.0.x to Vagrant 1.2.1.
When I type
vagrant up
, it now fails.vagrant halt
on a suspended VM works fine.I get this beaut:
Does anything look wrong with my configuration? I have ensured that
vagrant --version
shows 1.2.1, I've restarted all terminals, I've uninstalled the roguevagrant
gem that was in RVM (but that wasn't being run from the failing terminal anyway), and I have converted my Vagrantfile configuration to version 2. I checked that the box does indeed appear invagrant box list
(it does). I haven't tried to re-add it because I'm not clear how I would go about that. If it's invagrant box list
, then Vagrant should know about it, no?So, having done some due diligence, I turn to the issue queue. I hope it's just something stupid I did at some point. That would be the ideal resolution. I'll keep trying stuff in the meantime.
The text was updated successfully, but these errors were encountered: