-
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
Packaged puppet manifest, vagrantfile, and modules not copied on vagrant init #344
Comments
Crohr, Ah, so this is a common misconception, but you're about halfway right :) Files that are included with the boxes aren't unpacked into the project directory during a Best, |
Thanks for your answer, here is the Vagrantifle included in the box:
|
Sorry I took so long to respond. So what you want to change, this will be slightly confusing, sorry, but:
The reasoning for this is that this will get the modules directory relative to the packaged Vagrantfile, rather than the Vagrant environment. I'm looking into a better way to do this. |
I think this tip could be in the documentation until a better solution is available. |
Agreed on docs. |
Just an idea, the "better way to do this" is for Vagrant to automatically provide access to the include files via the I'm hacking it like this in my packaged
|
So "vagrant init" will not extract the Vagrantfile that I had packer include in the box? My Vagrantfile looks like the following (sorry that there is strange formatting/markdown): -- mode: ruby --vi: set ft=ruby :All Vagrant configuration is done below. The "2" in Vagrant.configureconfigures the configuration version (we support older styles forbackwards compatibility). Please don't change it unless you know whatyou're doing.required_plugins = %w(vagrant-vbguest vagrant-cachier vagrant-proxyconf) plugins_to_install = required_plugins.select { |plugin| not Vagrant.has_plugin? plugin } $script = <<SCRIPT Vagrant.configure("2") do |config|
end |
Hi,
Maybe it's me, but when you package puppet manifests and modules in a new base box with:
then:
and:
A default Vagranfile is generated, and when I try to do a
vagrant up
it fails saying it cannot find the manifests nor the modules:I can see that my included files have been correctly extracted to
~/.vagrant/boxes/centos5-x64/include/
(onvagrant add
), but I don't understand how I can correctly initialize that box. Am I doing something wrong? I thought the included files would be copied in mywhatever
directory onvagrant init centos5-x64
command.The text was updated successfully, but these errors were encountered: