Automate cloud-init ready template creation across 9 Linux families. No config files, no manual steps — just one command.
root.
Requires Proxmox VE 8.1+ on amd64.
Features
Built for Proxmox administrators who need repeatable, reliable template creation without manual CLI gymnastics.
Interactive menus guide you through every option. Default mode produces a ready-to-clone template in minutes.
Automatically finds the next available VM ID from 1001, skipping all existing containers and VMs.
Injects cloud-init, SSH server, and qemu-guest-agent into the image offline — every template is fully configured before first boot.
Built-in end-of-life detection warns before building templates from unsupported OS versions with no security patches.
Quick defaults for speed, or full control over CPU type, disk cache, bridge, VLAN, MTU, and MAC address.
Verifies root access, PVE version, architecture, and storage availability before making any changes.
Supported Distributions
All images are official cloud builds pulled directly from vendor-maintained CDNs.
How It Works
Paste the wget or curl one-liner into your Proxmox shell. No installation needed.
Interactive menus let you pick the distribution, version, and either default or advanced settings.
SSH, qemu-guest-agent, and cloud-init are injected into the disk image offline — before it ever touches Proxmox.
The image is imported, the VM is locked as a read-only template, and you can qm clone it instantly.
FAQ
whiptail dialog rendering. The Proxmox web console provides a stable, fully-interactive terminal that ensures menus display and respond correctly.
x86_64 / amd64 only. All referenced cloud images are amd64 builds. For ARM64 Proxmox support, see the asylumexp/Proxmox project.
cloud.debian.org, cloud-images.ubuntu.com, repo.almalinux.org, download.rockylinux.org, yum.oracle.com, cloud.centos.org, dl.fedoraproject.org, download.opensuse.org, and dl-cdn.alpinelinux.org. No third-party mirrors are used.
trap handlers for ERR, SIGINT, and SIGTERM. If creation fails, the partially created VM is automatically destroyed and the temporary working directory is cleaned up.