qm-template
A Python CLI that downloads cloud images and creates Proxmox VE VM templates with Cloud-Init support.
Features
- Multi-distro downloads: Debian, Ubuntu, Rocky Linux, AlmaLinux, Fedora, CentOS Stream, Alpine, openSUSE and Arch Linux
- Checksum verification: SHA-256/SHA-512 fetched from each distro's official
checksum files and saved next to the image (
<image>.sha256/.sha512) - Pinned builds: dated builds are selected where the upstream offers them, and images mirror the upstream directory layout
- Resumable downloads: uses
axel,aria2c,wgetorcurl, whichever is available, with a configurable number of parallel connections, progress output by default (silence it with--quiet) and a from-scratch retry when a download fails or fails checksum verification - Retrying metadata fetches: checksum and directory listings survive transient 5xx/network errors with exponential backoff
- Local image inventory:
qm-template imageslists downloaded images with their size and checksum sidecar, and--pruneremoves superseded dated builds and orphaned checksum files - Complete
qm createcommand: the whole template is assembled into a singleqm create ... --template 1invocation instead of a chain ofqm setcalls - Automatic VM IDs: the next free ID is picked from
qm list(or the Proxmox config directory), starting atcreate.start_id(default 9000) - Configurable CPU type:
create.cpu/--cpuoverrides the defaultcputype=hostwhen migration across CPU generations matters - TOML configuration: read with
tomllibfrom the standard library - Standard library only: Python >= 3.11; external commands are limited to
the downloader and the Proxmox VE
qm/pvesmtools
Requirements
- Python >= 3.11
- uv to install and develop
- A Proxmox VE host, normally running as root
- Proxmox VE (
qm,pvesm) for thecreatecommand - One of
axel,aria2c,wgetorcurlfor thedownloadcommand
Installation
Install the CLI as a uv tool:
uv tool install qm-template
For development, sync the project and run it from the virtual environment:
uv sync --group dev
uv run qm-template --help
Configuration
The configuration file is optional and loaded from
/etc/qm-template/config.toml. It is created with the built-in defaults on
first run; use --config PATH or QM_TEMPLATE_CONFIG to point elsewhere.
Downloaded images are stored in /var/lib/qm-template unless
paths.images_dir overrides it, mirroring the upstream layout:
<images_dir>/<distro>/<release>/[<tag>/]<filename>
download.preferred orders the downloaders and download.connections sets the
number of parallel connections for axel and aria2c. Downloads show progress
by default; set download.quiet = true or pass --quiet to hide it.
create.cpu sets the CPU type passed as cputype=... (default host).
create.start_id and create.step drive automatic VM ID selection (default
9000 and 1). create.sshkeys lists inline SSH public keys and
create.sshkeys_files lists key files; the contents of both are merged and
deduplicated by key fingerprint for Cloud-Init, and at least one key is
required. To create the file manually instead:
install -d /etc/qm-template
cp qm-template.example.toml /etc/qm-template/config.toml
Command-line options override the configured defaults.
Usage
Download a cloud image
# default distro from the configuration file
qm-template download
# pick a distro, optionally override parameters
qm-template download debian
qm-template download ubuntu --release noble --variant minimal
qm-template download debian --release bookworm --tag 20260907-2594
# print the first available downloader's command without running it
qm-template download --dry-run alpine
# hide the downloader progress output
qm-template download --quiet alpine
# list downloaded images with size and checksum sidecar
qm-template images
# remove superseded dated builds and orphaned checksum files
qm-template images --prune
# list distros and their configured defaults
qm-template distros
--dry-run resolves the image and pretty prints the command of the first
available downloader, one argument group per line, without downloading anything.
Builds are pinned where the upstream provides dated snapshots (Debian, Ubuntu
server, Arch Linux, openSUSE Tumbleweed): the newest build is selected, and a
newer build is downloaded alongside the old one instead of overwriting it.
Interrupted downloads are resumed on the next run; partial files are stored as
<image>.part. A failed download falls back to the next configured downloader
and is retried from scratch; a completed download that fails checksum
verification is downloaded once more from scratch before the command fails.
Checksum files and directory listings are retried with exponential backoff on
transient 5xx and network errors. The checksum fetched from the upstream source
is saved next to the image as <image>.sha256 or <image>.sha512, depending on
the upstream algorithm.
qm-template images [pattern] prints one line per image with a human-readable
size and the checksum sidecar algorithm. --prune removes older builds whose
names differ only in build dates/versions, together with their checksum
sidecars, plus checksum files whose image is gone; it asks for confirmation
unless --yes is passed, and --dry-run only lists the files it would remove.
Create a VM template
# interactive image selection; the VM ID is chosen automatically
qm-template create
# filter images with a regular expression on the relative path
qm-template create debian-13
# non-interactive with an explicit ID
qm-template create --vm-id 9000 --vm-name debian-13-template
# use a migration-friendly CPU type
qm-template create --cpu x86-64-v2-AES
# inspect the assembled command without running it
qm-template create --dry-run --vm-id 9000
When --vm-id is omitted, qm-template collects the IDs in use from
qm list (falling back to /etc/pve/qemu-server/*.conf) and picks the first
free ID at or after create.start_id (default 9000), advancing by
create.step (default 1); the 9000+ range keeps templates away from regular
VMs. If qm create fails, an existing but incomplete VM config is reported with
the qm destroy command needed to clean it up.
The resulting command is a single qm create invocation, which --dry-run
pretty prints as:
qm create 9000 \
--name debian-13-template \
--cpu cputype=host \
--cores 1 \
--balloon 1024 \
--memory 1024 \
--net0 model=virtio,firewall=1,bridge=vmbr0 \
--scsihw virtio-scsi-single \
--agent type=virtio,enabled=1 \
--machine q35 \
--ostype l26 \
--serial0 socket \
--vga serial0 \
--scsi0 local-lvm:0,import-from=/path/to/image.qcow2 \
--scsi1 local-lvm:cloudinit \
--boot order=scsi0 \
--ipconfig0 ip=dhcp \
--ciupgrade 0 \
--ciuser debian \
--cipassword debian \
--sshkeys ~/.ssh/id_ed25519.pub \
--template 1
Supported distros
| Name | Default release | Default variant | Notes |
|---|---|---|---|
debian |
trixie |
genericcloud |
--release accepts -backports |
ubuntu |
resolute |
server |
variant minimal also supported |
rocky |
10 |
GenericCloud |
variant GenericCloud-LVM |
almalinux |
10 |
GenericCloud |
variant GenericCloud-ext4 |
fedora |
44 |
Generic |
variant UEFI-UKI |
centos |
10 |
GenericCloud |
CentOS Stream |
alpine |
3.24 |
generic |
BIOS firmware, Cloud-Init enabled |
opensuse |
tumbleweed |
Minimal |
--release 15.6 for Leap |
archlinux |
latest |
cloudimg |
variant basic also supported |
Development
uv sync --group dev
just lint # ruff check --fix + ruff format
just typecheck # ty check src/
just test # pytest
just docs-build # mkdocs build
Project layout:
qm-template/
├── pyproject.toml
├── qm-template.example.toml
├── src/qm_template/
│ ├── cli.py # argument parsing and entry point
│ ├── commands.py # download / create / images / distros commands
│ ├── config.py # TOML settings and first-run config seeding
│ ├── checksum.py # checksum parsing and verification
│ ├── config.default.toml # default configuration shipped in the wheel
│ ├── download.py # axel / aria2c / wget / curl wrappers
│ ├── http.py # HTTP helpers, retries and directory listings
│ ├── images.py # local image inventory and pruning
│ ├── log.py # logging setup
│ ├── pve.py # qm/pvesm integration and VM ID selection
│ ├── shell.py # grouped command rendering and execution
│ └── distros/ # one module per distro family
└── tests/
Documentation
The published documentation site lives at https://ak1ra-lab.github.io/qm-template/.
References
Metadata
Release files for qm-template 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| qm_template-0.2.0.tar.gz | 105.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| qm_template-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 136.8 kB
Release files / qm_template-0.2.0.tar.gz
| Download URL | qm_template-0.2.0.tar.gz |
|---|---|
| Size | 105.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8edad52374ace43d8f91860dc741fc65289a7ffd5ee1fe7d7bdfc8eeb517c9dc
|
|
BLAKE2b-256 checksum How to use checksums |
23a1ee405bccb1dbef81cd550b69775546af9ffd2c897470126c0a860d3914e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency logRelease files / qm_template-0.2.0-py3-none-any.whl
| Download URL | qm_template-0.2.0-py3-none-any.whl |
|---|---|
| Size | 31.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7f6e28d1c80ea94e22cff61d901a000f694a97d1fe8f37a1769b5e2c953f0bb7
|
|
BLAKE2b-256 checksum How to use checksums |
46d6ca91f74f1819969f9365b2c947efcfb8a53e02d09fd2fc593da840405610
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 14, 2026.
Transparency log