-
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 package --base fails #5310
Comments
I have the same error with vagrant 1.7.2, ruby 2.1.2p95, chefdk 0.3.6 while packagine a Centos 7 base box.
|
Workaround for vagrant 1.7.2 : Test OK : |
@cdelaitre Thanks for the workaround. |
cdelaitre, thank you very much for sharing the workaround. |
Same problem while packaging a CentOS 7 box with Vagrant 1.7.4 on a Windows 7 host. My current workaround is NOT to setup port forwarding for the VM's port 22. |
Fixed! :) |
"vagrant package --base [server name]" is generating the following errors;
AFAICT, Vagrant::Machine#data_dir is coming back as nil which, according to the comments in lib/vagrant/machine.rb shouldn't happen.
It seems as though plugins/commands/package/command.rb might need a default value for data_dir to pass into Vagrant::Machine.new, but that's as far as I could get in figuring out how to fix this.
More details and full log & backtrace are below.
David
This is my Vagrantfile;
Then;
...and boom.
This is using Vagrant 1.7.2 and Ruby 2.2.0 with VirtualBox 4.3.20r96996 on a Mac running OS X 10.9.5 (I got the same result using Ruby 1.8.7)
Log and backtrace;
The text was updated successfully, but these errors were encountered: