Closed boeboe closed 4 years ago
I bet that log message is being truncated and it's supposed to read "relative addresses not allowed" . Is this still an issue with the most recent version of Packer?
@SwampDragons will test with latest version on ubuntu as well. I had a similar issue with the latest version on macos, but wasn't sure it was the same issue based on the error logs.
Same issue on latest packer on ubuntu.
Hi @boeboe thanks for the instructions on the ISO installation; it takes a long for sure. I'm still working on reproducing locally, but while waiting I did mange to find an issue reported on the F5 forums which may be relevant here https://cdn.f5.com/product/bugtracker/ID819429.html (originally posted here).
The virtualbox builder will try to upload a version box file into the home directory of the connecting user, which in this case happens to be /root. If the bug above is still an issue for BIGIP-14.0.1.1-0.0.6
it can explain the error we are seeing here.
With that said, if you try adding the virtualbox_version_file
configuration option and setting it to a path like /var/tmp/.vbox_version
do you receive this error?
If the file is not needed you can also set virtualbox_version_file
to an empty string to prevent the builder from uploading this file entirely. See virtualbox_version_file for more info.
Hi @boeboe I had a chance to repro this issue and verify that setting virtualbox_version_file
to either an empty string or /var/tmp/.vbox_version
results in a successful build; confirming that the guest OS allows for the copying of files into certain directories.
I’m going to close this issue since it’s not an issue with Packer, and look to see if there is room for updating the error message to point users to the virtualbox version file documentation.
If you end up needing more help with this kind of initial configuration, the mailing list or community forum are generally more useful. Issues opened here on the Packer issue tracker are only viewed by a small handful of developers who work on the tool, and we don't always have the most depth or experience when it comes to custom issues with particular build configurations.
Cheers!
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Packer: v1.3.3 VirtualBox: 6.0.16 r135674 (Qt5.9.5) OS: Ubuntu 18.04.3 LTS
Output traces of builder: _PACKERLOG=1 packer build template-virtualbox.json
Packer file:
ISO image available here. You will need to login with root/default, change pw to something none trivial and then finally change root pwd to vagrant to bypass the pw restrictions and allow packer to login as root/vagrant. Warning, the while installation process takes quite some time. This double PW change is not automated and needs to be done manually, while packer is retrying to connect over ssh.
Note: the same works well for builder type Qemu, so it is a specific VirtualBox builder issue.