Home / Lab / Homelab Setup / Why I Built a Home Lab on a Gaming Laptop
Complete Homelab 5 min read · Part 1 of the Homelab Setup series

Why I Built a Home Lab on a Gaming Laptop

Running Proxmox on a gaming laptop turns out to be a surprisingly capable home lab setup — enough CPU, ECC-free RAM that doesn't matter for learning, and a screen attached. Here's why I did it and what I learned.

March 10, 2025
Proxmox VEUbuntu ServerDockerTailscale

Most home lab guides assume you have a decommissioned server rack, three Raspberry Pis, or at least a NUC sitting around. I had a gaming laptop I wasn’t using for gaming anymore and a Sunday afternoon with nothing scheduled.

So I turned it into a lab.

Why a Laptop?

The obvious objection is thermals. Gaming laptops run hot under sustained load, and Proxmox under production-like conditions is sustained load.

The less obvious answer: for learning purposes, it doesn’t matter. The goal isn’t uptime SLAs. The goal is hands-on reps with technologies I use at work — Kubernetes, networking, storage — in an environment where breaking things costs nothing.

A laptop also has a few underrated advantages:

  • Built-in UPS: The battery means a power cut doesn’t corrupt your ZFS pool
  • Built-in display: No KVM or serial console needed when things go wrong
  • Portable: Move it between rooms, offices, or countries

The Setup

I’m running Proxmox VE 8.x directly on the hardware. Inside Proxmox, I have:

  • 2 Ubuntu Server VMs — for Kubernetes experiments (one control plane, one worker)
  • 1 Debian LXC — running Home Assistant and a few Docker containers
  • 1 TrueNAS SCALE VM — for NFS storage shared back to the other VMs

The laptop has 32GB RAM and a 6-core CPU, which is more than enough to run all of this simultaneously at reasonable utilization.

Networking

I use Tailscale to stitch the lab into my personal network without punching holes in my home router. Every VM gets a Tailscale node, so I can reach them from anywhere without exposing anything to the internet directly.

For internal networking, Proxmox’s built-in bridge (vmbr0) gives each VM its own IP on my LAN.

What I’ve Used It For

  • Testing Kubernetes upgrade paths before recommending them to clients
  • Running local LLMs via Ollama (covered in a separate post)
  • Experimenting with Cilium as a CNI plugin
  • Breaking and rebuilding DNS configurations without impacting anything real
  • Running integration tests for infrastructure code locally before pushing

What Broke

The laptop fans run at 60-70% under normal lab load. The thermals are fine — it throttles gracefully — but it’s not silent. If you care about noise, a mini-PC like a Beelink or an old Optiplex is a better choice.

I also had to disable the discrete GPU in the BIOS to reduce idle power draw. Proxmox doesn’t need it, and it was adding about 20W of heat for no reason.

Would I Recommend It?

For learning: absolutely. If you have a laptop that’s otherwise sitting in a drawer, repurposing it as a Proxmox host is a weekend project that keeps paying dividends for months.

For anything production-adjacent: get proper hardware. The thermal envelope of a laptop isn’t designed for 24/7 sustained load at high CPU utilization. Mine handles it fine, but I wouldn’t stake anything important on it.

The barrier to a home lab is lower than most people think. You don’t need a rack. You don’t need to spend money. You need hardware that already exists and the willingness to reinstall an OS.

Discussion