Releases: client-api/proxmox-docker
Releases · client-api/proxmox-docker
Release list
v1.0.0
Test-only Docker images for the four Proxmox products — built so SDK clients generated from the Proxmox OpenAPI specs can be E2E-tested against a real Proxmox API surface inside GitHub Actions.
Images
Published to GHCR; pull with the documented tag policy (see `VERSIONING.md`).
| Product | Image |
|---|---|
| Proxmox VE 9.2.x | `ghcr.io/client-api/proxmox-docker/pve-test:9.2` |
| Proxmox Backup Server 4.2.x | `ghcr.io/client-api/proxmox-docker/pbs-test:4.2` |
| Proxmox Mail Gateway 9.x | `ghcr.io/client-api/proxmox-docker/pmg-test:9` |
| Proxmox Datacenter Manager 1.0.x | `ghcr.io/client-api/proxmox-docker/pdm-test:1.0` |
Highlights
- Real systemd as PID 1 in PVE — supports the full `qm` and `pct` lifecycle.
- Fixture VM (`tiny-test`, vmid 100) backed by the 256-byte-vm release; fixture CT (`tiny-ct`, vmid 200) backed by Alpine 3.21 minirootfs.
- KVM lifecycle works when the runner exposes `/dev/kvm`; LXC lifecycle works when the host kernel runs cgroup v2.
- Ticket + token auth seeded on every boot, written to `/run/credentials.json` in a product-agnostic shape (use `token_header_value` directly — PVE/PMG use `=`, PBS/PDM use `:` between token id and value).
- Per-product `docker-compose.yml` and a dedicated `client-api/proxmox-docker-action` GitHub Action for downstream consumption.
Tag scheme
- `latest`, `` (e.g. `9.2.2`), `.` (e.g. `9.2`) — stable channel
- `dev`, `dev-` — upstream `*-test` channel, nightly rebuild
Not for production
These images run with hard-coded credentials, self-signed TLS, and `--privileged`. Do not expose them to the public internet.
License: Apache 2.0