Closed Joseph-R closed 9 years ago
Hi @JoeReid-Korrelate
I am sorry you are having problems with Vagrant. Can you please uninstall all plugins and see if the problem persists?
Hey Seth! Big fan of your blog, man. I appreciate your help on this.
I see plugins in the --debug output (linked above) that do not show up in a vagrant plugin list
.
INFO global: Plugins:
INFO global: - bundler = 1.7.11
INFO global: - mime-types = 1.25.1
INFO global: - rdoc = 4.0.0
INFO global: - rest-client = 1.6.8
INFO global: - vagrant-share = 1.1.3
$ vagrant plugin list
vagrant-share (1.1.3, system)
Attempted to uninstall the only plugin listed (vagrant-share), which resulted in the following output:
$ vagrant plugin uninstall vagrant-share
Uninstalling the 'vagrant-share' plugin...
The plugin you're attempting to uninstall ('vagrant-share') is a
system plugin. This means that the plugin is part of the installation
of Vagrant. These plugins cannot be removed.
You can however, install a plugin with the same name to replace
these plugins. User-installed plugins take priority over
system-installed plugins.
Attempted to upgrade vagrant-share, just in case:
[11:17:50] (7) jreid@JoesMacBookPro:~/repo/chef-repo/cookbooks/JO2O(migrate_dev_environment_JR)
$ vagrant plugin update vagrant-share
Updating plugins: vagrant-share. This may take a few minutes...
All plugins are up to date.
The --base
flag is a bit weird, and must only reference the name of a VM in the VirtualBox GUI. To package it otherwise, run vagrant package
directly.
I am unable to package base boxes using Vagrant 1.7.2.
Global status shows name "default".
But attempts to CD into that directory and package the VM with
vagrant package --base $name
fail with the following:Debug output.
Versions:
I'm not sure if I'm doing something wrong, or if there is a bug. I used to be able to pack boxes like this with a previous version of Vagrant. Do I need to do something different now?