Nodes¶
Nodes are Proxmox VE servers within a site that host containers.
Node Properties¶
- Name: Must exactly match the Proxmox hostname
- IP Address: For internal DNS resolution
- API URL: e.g.,
https://192.168.1.10:8006 - Authentication: Username/password or API token
- TLS Verification: Enable/disable certificate validation
- Template Storage: Proxmox storage for CT template images (
vztmplcontent) - Root Disk Storage (
volumeStorage): Proxmox storage for container root filesystems (rootdircontent); thin-provisioned block storage (LVM-thin, Ceph RBD, ZFS) is fine - Shared Volume Storage (
sharedVolumeStorage, optional): path-backed shared filesystem (CephFS, NFS) hosting persistent volumes. When blank, volumes fall back to the root disk storage
Shared volume storage should be shared across the cluster
Persistent volumes require their host directories to exist on whichever node a container lands on. Set shared volume storage to storage that is shared across every node (a path-backed shared filesystem such as CephFS or NFS). On save, the manager warns (but does not block) if the chosen shared volume storage is not shared or is not active on every node. Single-node sites are unaffected.
Adding Nodes¶
Import Nodes (Recommended)¶
Discovers all nodes in a Proxmox cluster automatically:
- Navigate to Nodes → select site → Import Nodes
- Enter API URL of any node, credentials, and TLS setting
- Click Import — all cluster nodes are discovered and imported
Tip
Import only needs credentials for one node. It discovers all other nodes in the same cluster.
Manual Node Creation¶
- Navigate to Nodes → select site → Create New Node
- Enter name (must match Proxmox hostname exactly), IP, API URL, and credentials
Important
Name mismatches cause API communication failures.
Authentication¶
Use root@pam credentials for both import and manual node creation. The Proxmox API requires root-level access to configure container settings needed for nested containerization.
Username & Password:
Username: root@pam
Password: your-root-password
TLS Verification¶
Proxmox uses self-signed certificates by default. Either disable TLS verification (acceptable for isolated networks) or install valid certificates from a trusted CA (recommended for production).
Managing Nodes¶
- Edit: Update credentials or settings from the node detail page
- Delete: Remove a node (must have no active containers first)
- Multi-node: Proxmox supports HA features — see Proxmox HA docs
Storage Configuration¶
Nodes have separate storage settings because most Proxmox storage types only support one content type, and because root disks and persistent volumes need different semantics (block vs. filesystem).
| Setting | Content Type | Default | Purpose |
|---|---|---|---|
| Template Storage | vztmpl |
local |
Stores pulled Docker/OCI images as CT templates |
| Root Disk Storage | rootdir |
local-lvm |
Stores container root filesystems |
| Shared Volume Storage | path-backed FS | (root disk storage) | Hosts persistent volumes under <path>/volumes |
If a configured storage does not support the required content type, the system falls back to the largest enabled storage on the node that does. If no storage supports the required content type, container creation fails.
To verify storage content types in Proxmox, navigate to Datacenter → Storage and check the Content column.