Packer configuration for creating Debian virtual machine templates for Proxmox VE.
- Packer 1.9.1+
- Proxmox VE 6.2+
Launching a virtual machine requires an operating system to be installed. VM installation is usually done using an ISO image file and depending on the OS, this can be a time consuming task one might want to avoid. Luckily, this can be automated using a process known as preseeding.
Preseeding provides a way to answer questions asked during the installation process, without having to manually enter the answers while the installation is running. You can check out the configuration for a standard Debian installation in preseed.cfg and read more about this method in the preseed documentation.
Proxmox Templates provide an easy way to deploy many VMs of the same type, but naturally we don't want them to be completely identical. They may need a different hostname, an IP address, etc. This is what cloud-init takes care of.
Cloud-init is used for initial machine configuration like creating users or preseeding
authorized_keysfile for SSH authentication. You can check out the configuration in cloud.cfg and read more about this in cloud-init documentation.
🚨 IMPORTANT! 🚨
Do not forget to replace ssh_authorized_keys in cloud.cfg with your own public keys as otherwise you won't be able to log in to the machine since cloud-init is configured to set the root password to a random one after the template has been built.
The public SSH keys will added to a password-less sudo user named debian.
Templates are created by converting an existing VM to a template. As soon as the VM is converted, it cannot be started anymore. If you want to modify an existing template, you need to create a new template.
Here's how to do all that in one step:
$ packer build -var-file example-variables.pkrvars.hcl .
proxmox: output will be in this color.
==> proxmox: Creating VM
==> proxmox: No VM ID given, getting next free from Proxmox
==> proxmox: Starting VM
...
==> proxmox: Stopping VM
==> proxmox: Converting VM to template
Build 'proxmox' finished.
==> Builds finished. The artifacts of successful builds are:
--> proxmox: A template was created: 102📚 Tip!
Packer automatically loads any var file that matches the name *.auto.pkrvars.hcl, without the need to pass the file via the command line. If you rename the example variable definitions file from example-variables.pkrvars.hcl to example-variables.auto.pkrvars.hcl, then you can run the build just by calling:
$ packer build .Right-click the template in Proxmox VE, and select "Clone".
- full clone is a complete copy and is fully independent from the original VM or VM Template, but it requires the same disk space as the original
- linked clone requires less disk space but cannot run without access to the base VM Template. Not supported with LVM & ISCSI storage types
You can contribute in many ways and not just by changing the code! If you have any ideas, just open an issue and tell me what you think.
Contributing code-wise - please fork the repository and submit a pull request.
MIT