-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Failed to retrieve the preconfigureation file #193
Comments
The http_directory is incorrect since it is relative to where the command is run from, as well. There is another issue to make this nicer, #54 |
Oh also, you don't need |
Ok, thank you for the feedback. I'll upgrade, make the additional adjustments and try again. Thanks! |
Hello |
@Legend in my case - very similar issue - turn off the firewall |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello, I'm running into an error when generating vbox and vmfusion images from a veewee definition file converted by veewee-to-packer. I'm getting "Failed to retrieve the preconfigureation file" errors from both applications during the installation process when running packer with the converted template.json file. Using veewee, the VM is created successfully for this definition.
Has anyone else encountered this? Is there a way to work around it?
Steps to reproduce what I'm seeing:
veewee-to-packer /full/path/to/veewee/templates/ubuntu-12.04.2-server-amd64-netboot/definition.rb
This generates a template.json file successfully (see below #template.json).
Modify the provisioners section of the template.json file to have the full path of for the scripts listed. This is related to Make paths in templates relative to the template #54
Modify each builder definition to include an "iso_md5" key/value pair.
"iso_md5": "1278936cb0ee9d9a32961dd7743fa75c",
./packer build /full/path/to/veewee/output/template.json
The text was updated successfully, but these errors were encountered: