Proxmox Homelab Setup Guide

Why Proxmox

Proxmox VE is the homelab virtualization standard. It runs full virtual machines and lightweight LXC containers side by side, supports ZFS, has a clean web UI, and includes powerful backups — all free and open source. It lets one physical machine safely host many isolated systems. See how it stacks up in Proxmox vs VMware.

Step 1: Check hardware and enable virtualization

A CPU with VT-x/AMD-V (and VT-d/AMD-Vi if you want PCI passthrough).
Enough RAM for your VMs plus ZFS ARC (16–32 GB is a comfortable start).
Enable virtualization (and IOMMU, if needed) in the BIOS/UEFI.

Step 2: Install Proxmox VE

Download the Proxmox VE ISO and write it to a USB stick.
Boot from it and follow the installer.
Choose your root disk filesystem — ZFS (even single-disk or mirror) is a great choice for snapshots and integrity.
Set a static IP, hostname and strong root password.

After install, browse to https://your-server-ip:8006.

Step 3: First-boot housekeeping

Repositories: if you don't have a subscription, switch to the no-subscription repo so updates work, then apt update && apt full-upgrade.
Updates: keep the host patched.
Users: create a non-root admin user and enable two-factor authentication for the web UI.

Step 4: Plan storage

Separate concerns for reliability and performance:

OS disk — the Proxmox install itself (a small SSD is fine).
VM/container storage — ideally a separate SSD, as a ZFS pool or LVM-thin.
Bulk storage — large HDDs, often passed to a NAS VM.

If you want a TrueNAS VM to manage disks directly, use an HBA in IT mode and pass it through rather than passing individual disks.

Step 5: Networking

The default vmbr0 bridge connects VMs to your LAN. For more advanced setups:

Create VLAN-aware bridges to segment traffic (e.g. an isolated IoT network).
Consider a dedicated NIC for storage traffic if you run heavy VM disk I/O over the network.

Step 6: VMs vs. LXC containers

Choose the right tool:

LXC containers — lightweight, share the host kernel, boot instantly, use minimal RAM. Perfect for lightweight Linux services.
VMs — full isolation with their own kernel. Use for Windows, TrueNAS, a hardened Docker host, or anything needing PCI passthrough.

A popular pattern: one VM as a dedicated Docker host for all your containers, plus a few LXCs for specific services.

Step 7: Create your first VM with cloud-init

Use a distro cloud image plus cloud-init to make reproducible VMs:

Download an Ubuntu/Debian cloud image.
Create a VM, import the disk, and attach a cloud-init drive.
Set the user, SSH key, and IP in the cloud-init tab.
Convert it to a template and clone new VMs from it in seconds.

Step 8: Set up backups

Don't skip this. Configure Proxmox backups:

Add a backup storage target (NFS on your NAS, or Proxmox Backup Server for dedup + verification).
Schedule a daily job with sensible retention.
Test a restore — a backup you've never restored is just hope.

Step 9: Snapshots and updates workflow

Before any risky change inside a VM, take a snapshot so you can roll back instantly. Combined with backups, this makes upgrades low-stress.

Common beginner mistakes

Passing individual disks to a NAS VM instead of an HBA (bypasses SMART/ZFS health).
Running everything as separate VMs (LXCs are lighter for simple services).
No backups, or backups on the same disk as the VMs.
Forgetting the no-subscription repo, then wondering why updates fail.

Next steps

With Proxmox running, spin up a Docker host VM and deploy services following Docker Compose best practices, then add monitoring to keep an eye on it all.