Conversation
| - exec_local: | | ||
| MNT=$(mktemp -d) | ||
| sudo mount -o loop,offset=32768 $${image_disk}.$${image_format} $MNT | ||
| sudo tar -czf $${appliance_filename}.tgz -C $MNT . | ||
| sudo chmod 666 $${appliance_filename}.tgz | ||
| sudo umount $MNT | ||
| rm -r $MNT |
There was a problem hiding this comment.
This step makes running the kameleon build command require the root privileges, which is not necessary for any other recipe. Rather use the export_appliance helper (which uses guestmount but does not need root privileges).
There was a problem hiding this comment.
The build VM is not bootable (bootloader installed ?). As a result, guestmount does not work for the export.
Since we would like to possibly export qcow files as well, making the qcow file bootable seems a good idea.
There was a problem hiding this comment.
guestmount is not looking for a bootloader but for vmlinuz and initrd files to extract and use directly within qemu. This seems to not function with nixos partitioning / non-standard file hierarchy. Need to dive in and find out how to possibly give some insight to guestmount with its -m option.
npf
force-pushed
the
nixos19.09
branch
2 times, most recently
from
53ff675 to
c745bbe
Compare
|
In and Out context are not defined. Only the |
So that the key is available to be sent to the 1st VM possibly.
- Have the ssh keys readly before the installer runs, so that they can be used right away in the installer. - Start http before preparing the autoinstall script, so that the HTTP_PORT is known and can be http service can be used in the autoinstall script.
…not work with nixos) Do not use virt-customize to push the ssh key of root because that does not work with nixos, push it earlier in the autoinstall script.
…age. This should be done before export, not right away, so that debugging in the qemu vnc console is possible.
2 participants
No description provided.