Dear Proxmoxers,
I thought I could run some kind of pve-autoinstall-iso-creator-machine, that generates autoinstall-iso files for various PVEs, until I noticed:
Installing an auto-install-iso (generated on e.g. hostname "pve-iso-creator.example.com") on another machine its host/nodename is pve-iso-generator, too. In other words, the hostname of the machine the proxmox-auto-install-assistant has been run seems to be hardcoded into the resulting autoinstall-iso.
Question: Is there any easy way to set the hostname during iso-creation (eg. via the answers.toml) or afterwards during first boot (e.g. via dns reverse lookups) or something else?
If there are no such options - neither implemented, nor planned - what do you think, sound this workaround procedure promissing:
1. deploy e.g. a minimalistic debian lxc (e.g. bookworm netinstall)
2. add the pve-repositories
3. install proxmox-auto-install-assistant
4. rename the lxc's hostname into new-pve.example.com
5. generate an autoinstall-iso
6. download the autoinstall-iso
7. destroy the lxc
8. deploy the downloaded autoinstall-iso onto the new-pve.example.com
My main concerns are regarding step 4: Is it sufficient to change /etc/hosts and /etc/hostname? If not, what else does the proxmox-auto-install-assistant rely on, regarding the hostname an ISO sets?
Another idea could be using hostname assignment via dhcp, but I think the above steps are easier to automate.
Bonus question:
How do you [intent to] use the autoinstall-feature?
Thanks a lot for your feedback!
Best regards,
proxmix
I thought I could run some kind of pve-autoinstall-iso-creator-machine, that generates autoinstall-iso files for various PVEs, until I noticed:
Installing an auto-install-iso (generated on e.g. hostname "pve-iso-creator.example.com") on another machine its host/nodename is pve-iso-generator, too. In other words, the hostname of the machine the proxmox-auto-install-assistant has been run seems to be hardcoded into the resulting autoinstall-iso.
Question: Is there any easy way to set the hostname during iso-creation (eg. via the answers.toml) or afterwards during first boot (e.g. via dns reverse lookups) or something else?
If there are no such options - neither implemented, nor planned - what do you think, sound this workaround procedure promissing:
1. deploy e.g. a minimalistic debian lxc (e.g. bookworm netinstall)
2. add the pve-repositories
3. install proxmox-auto-install-assistant
4. rename the lxc's hostname into new-pve.example.com
5. generate an autoinstall-iso
6. download the autoinstall-iso
7. destroy the lxc
8. deploy the downloaded autoinstall-iso onto the new-pve.example.com
My main concerns are regarding step 4: Is it sufficient to change /etc/hosts and /etc/hostname? If not, what else does the proxmox-auto-install-assistant rely on, regarding the hostname an ISO sets?
Another idea could be using hostname assignment via dhcp, but I think the above steps are easier to automate.
Bonus question:
How do you [intent to] use the autoinstall-feature?
Thanks a lot for your feedback!
Best regards,
proxmix
Last edited: