Skip to main content

​
Proxmox provisioner backend

Track the planned Proxmox execution target. Proxmox is not supported for normal Nora deployments in the current release.
Proxmox is a roadmap execution target for Nora agents. The adapter work is present for continued development, but current releases keep Proxmox release-blocked in the runtime catalog. Use Docker or Admin-registered Kubernetes for supported deployments today. NemoClaw is available only as an experimental sandbox profile on supported targets. Deploy wizard — Execution Target picker with execution target options

​
Current status

Even if ENABLED_BACKENDS includes proxmox, Nora marks Proxmox as blocked and returns: 
Proxmox execution target is not supported in this Nora release.
The blocked target can stay visible for operator awareness, but it is excluded from normal onboarding and should not be used for production agent placement.

​
Adapter configuration reference

These settings are retained for adapter development and future validation. They do not make Proxmox a supported execution target in the current release. 
ENABLED_BACKENDS=proxmox

PROXMOX_API_URL=https://proxmox.local:8006/api2/json
PROXMOX_TOKEN_ID=user@pam!tokenname
PROXMOX_TOKEN_SECRET=<your-token-secret>
PROXMOX_NODE=pve
PROXMOX_TEMPLATE=local:vztmpl/ubuntu-22.04-standard_22.04-1_amd64.tar.zst
PROXMOX_ROOTFS_STORAGE=local-lvm
PROXMOX_BRIDGE=vmbr0
PROXMOX_SSH_HOST=proxmox.local
PROXMOX_SSH_USER=root
PROXMOX_SSH_PRIVATE_KEY_PATH=/run/secrets/proxmox_key
PROXMOX_TOKEN_ID must use Proxmox API token format: user@realm!tokenname.

​
Future required access

The API token and SSH user must be able to:
  • Clone or create containers from the configured template.
  • Start, stop, restart, and delete the runtime target.
  • Run bootstrap commands through pct during first deploy.

​
Future runtime-specific templates

OpenClaw uses PROXMOX_TEMPLATE. Hermes and NemoClaw need explicit templates when those runtime paths are enabled: 
PROXMOX_HERMES_TEMPLATE=
PROXMOX_NEMOCLAW_TEMPLATE=

​
Verification

Confirm the backend reports as blocked: 
docker compose up -d --build backend-api worker-provisioner
curl -fsS http://localhost:8080/api/config/platform
The response should show Proxmox as unavailable or blocked, while Docker and any Admin-registered Kubernetes targets remain the supported deployment paths.