Proxmox LXC: The Complete Self-Hosting Guide for 2026
homelab

Proxmox LXC: The Complete Self-Hosting Guide for 2026

Ricardo Gil
September 2, 2026
10 min read
#proxmox #lxc #self-hosting #homelab

I've been running Proxmox VE as my primary homelab hypervisor for over two years. In that time I've set up dozens of LXC containers β€” everything from a full media server stack to local LLMs to self-hosted Git infrastructure. This page is the index I wish I'd had when I started: every guide I've written, organized by what you're trying to accomplish.

If you're new to Proxmox, start at the top. If you already have a working Proxmox node and want to add a specific service, jump straight to the relevant section.

Why LXC Containers Over Docker on Proxmox?

This is the question I get asked most. The short answer: LXC containers are closer to lightweight VMs β€” they have their own init system, networking, and filesystem. Docker is an application runtime. On Proxmox, you can run either, and often you'll run both. My take after running both for years is in my full Docker vs LXC comparison, but for most self-hosted services, LXC is the right default on Proxmox.

LXC containers use far less RAM than full VMs, start in seconds, and integrate cleanly with Proxmox's backup and snapshot tooling. A Jellyfin container on my Beelink EQ12 (~$189) uses about 400MB idle. The same setup in a full Ubuntu VM would use 1.5–2GB.

Hardware: Where to Start

You don't need server hardware to run a serious Proxmox homelab. I started on a Dell OptiPlex 7090 β€” a $120 refurbished mini PC β€” and it handled 8 LXC containers without breaking a sweat. Now I run a Beelink EQ12 with 32GB RAM and a WD Black 2TB NVMe (~$129), which is more than enough for everything on this page.

The two things that matter most: RAM (get at least 16GB, 32GB if you want to run local AI) and a fast NVMe drive. My full mini PC buying guide for Proxmox covers the specific models I've tested.

Networking and Remote Access

Once you have Proxmox running, the first problem is remote access. You don't want to punch holes in your firewall for every service. These are the solutions I've actually deployed:

  • Tailscale on Proxmox β€” The easiest way to get secure remote access. Five-minute setup, zero port forwarding.
  • Headscale on Proxmox LXC β€” Self-hosted Tailscale control server for full control without depending on Tailscale's infrastructure.
  • NetBird on Proxmox LXC β€” Wireguard-based alternative to Tailscale/Headscale with a clean self-hosted option.
  • Cloudflare Tunnels β€” Best for exposing web services publicly without opening ports. I use this for anything I want accessible without a VPN.
  • Traefik v3 on Proxmox LXC β€” Automatic HTTPS for every service behind your firewall. The reverse proxy I run on everything.
  • OPNsense on Proxmox β€” If you want a proper firewall layer, this is how I set it up as a Proxmox VM.

I run Traefik + Headscale as the base stack. Traefik handles HTTPS for internal services; Headscale handles remote access. The TP-Link 2.5G USB Ethernet adapter (~$29) is worth getting if your mini PC only has 1GbE β€” makes a noticeable difference for NAS workloads.

Media and Files

This is what most people come to self-hosting for. Replacing streaming subscriptions and cloud storage with something you own and control.

Security and Authentication

Self-hosting means you're responsible for your own security. These are the two layers I consider non-negotiable:

AI and Local LLMs

Running AI locally on Proxmox is one of the most practical use cases in 2026. No API bills, no data leaving your network.

For local AI inference, RAM is everything. The Crucial 32GB DDR4 kit (~$59) is the upgrade I recommend first if you want to run 7B+ models comfortably.

Development Infrastructure

Monitoring and Management

Running 15+ containers means you need visibility into what's happening. These are the tools I actually keep open:

Automation

  • n8n 2.0 Self-Hosted β€” I run n8n as an LXC on Proxmox. It handles all my Claude automation workflows and costs nothing per task.

Where to Start If You're New

If you're building a Proxmox homelab from scratch, here's the order I'd follow:

  1. Pick your hardware β€” the mini PC guide will help
  2. Install Proxmox VE and create your first LXC container
  3. Set up Tailscale for remote access
  4. Deploy Traefik for HTTPS
  5. Add Vaultwarden for password management
  6. Then pick whatever services you actually want to use

Running this for your business?

I deploy self-hosted infrastructure and private AI stacks for small teams β€” Proxmox, Ollama, n8n, and more. Let's talk β†’

Ricardo Gil is a full-stack developer (.NET/Angular) with 6+ years of experience. He runs a personal homelab on a Beelink mini PC with Proxmox VE, self-hosting everything from Jellyfin to local LLMs with Ollama. More about Ricardo β†’
πŸ“¬Weekly Newsletter

Get the best home lab & AI content

No spam. One email per week. Unsubscribe anytime.

Share this article