Run Docker containers inside Proxmox LXC with full performance. Covers nesting, overlay2 on ZFS, privileged vs unprivileged tradeoffs, cgroup resource limits, and security hardening for production homelab workloads.
Build an unbooted cloud-image template and verify a disposable clone before extending provisioning.
Set deterministic ZFS ARC limits, add L2ARC without wasting RAM on metadata, and tune recordsize and compression for your Proxmox homelab VMs.
Complete Proxmox VE PCIe passthrough guide — GPU for Jellyfin transcoding, NVMe direct access, SAS HBA for NAS VMs. Kernel configs, vfio-pci, IOMMU groups, and working Proxmox VM settings.
Complete Linux sysctl kernel tuning guide for homelab servers. Network buffers, BBR congestion control, OOM management, fs.inotify limits, and Docker-specific sysctl configs.
If you run Proxmox VE, you’ve got two container runtimes at your fingertips — LXC (built into Proxmox) and Docker (nested in an LXC or VM). Both are “containers” in the broad sense, but they solve different problems. Picking wrong means performance you don’t need or isolation you don’t have. This post walks through the decision criteria, backed by configs from an existing homelab running Proxmox 8.x with VLAN segmentation. ...
ZFS snapshots preserve dataset state, but they are only one part of a recovery plan. Pool failure, lost guest configuration, and inconsistent application data need separate protection. This guide uses a small filesystem lab on an existing test pool. It does not create pools, repartition disks, or roll back running guests. Verification status Area Evidence and limits Technical review Official OpenZFS and Sanoid references reviewed on October 31, 2026. Static checks Bash examples syntax checked. Runtime No ZFS pool, dataset, snapshot, clone, replication, or recovery operation executed for this revision. Scope Proposed filesystem lab, not a captured host layout or measured performance result. 1. Identify the storage objects Proxmox offers several installation and storage choices; ZFS is not a universal default. Inspect the actual host before changing properties: ...
One PBS setup workflow: dedicated storage, authenticated PVE access, maintenance jobs, and an isolated restore test.
A Proxmox bridge connects guest interfaces to a network. VLAN filtering determines which VLANs traverse its ports. Routing and firewall policy determine which subnets may communicate. Start by documenting what the physical switch sends to the host. A correct guest VLAN tag cannot fix a mismatch on the uplink. Verification status Area Evidence and limits Technical review Reviewed against the official references below on October 31, 2026. Shell examples Bash syntax checked; no host networking commands executed. Configuration Illustrative single-uplink IPv4 lab, not a captured production configuration. Runtime Application, rollback, DHCP, guest traffic, and firewall behavior remain untested for this revision. 1. Identify the management path These two designs are different: ...
Historical setup: This article records the original lab deployment. Frigate configuration changes between releases; validate the configuration against the documentation for the exact image version you deploy. The example exposes several service ports and is intended for an isolated lab network. Restrict access at the host and router, and use the authenticated interface supported by your chosen release. Frigate is an open-source NVR built for real-time object detection with local processing. No cloud subscriptions, no vendor lock-in — just cameras, a GPU, and decent detection models. ...