PebbleRack

PebbleRack Lab Guides · 25 lessons

Build a lab you can understand and recover.

Start with one useful task. Use your existing computer where it fits, learn the tradeoffs, and add complexity only when it earns its place. Compare local AI with other routes.

Evidence status

These guides are checked against official documentation but have not been run end to end on a PebbleRack machine. Final PebbleRack hardware and software support are still being evaluated. Back up important data before changing a host.

foundations

Choose and prepare

Start with what you already own. Make one service work before adding complexity.

  1. 01Choose one home-lab goal you can proveDefine one useful local task, its boundaries, and a visible success test before buying or installing anything.
  2. 02Inventory and map what you already ownMake a private inventory and connection map so you can plan safely and troubleshoot later.
  3. 03Choose hardware, power, and airflow for the first labDecide whether an existing computer is enough and check the physical constraints before adding equipment.
  4. 04Plan addresses and names without disrupting your networkUse the existing router's DHCP service and record a stable way to find your lab host.
  5. 05Install Ubuntu Server LTS on a lab hostInstall Ubuntu Server 26.04.1 LTS on a clearly identified, backed-up machine and record a first-boot baseline.
  6. 06Use SSH keys for lab administrationSet up encrypted remote administration on the local network while keeping console recovery available.
  7. 07Establish a patching baselineRecord what updates automatically, when you will review changes, and how you will detect required restarts.
  8. 08Run a first containerized service on the hostInstall Docker Engine using its official Ubuntu repository and run a localhost-only test service with Compose.

proxmox

Build with Proxmox

Use a hypervisor only when isolated guests and recovery help your task.

  1. 09Choose Proxmox VE or Plain Linux for Your LabPick a host operating system based on the workloads and recovery work you actually need.
  2. 10Install Proxmox VE on a Dedicated Lab HostInstall Proxmox on a verified target while protecting existing data and access.
  3. 11Set Up a Safe Proxmox Management Network and BridgeUnderstand the default bridge and change networking without losing the host.
  4. 12Choose Proxmox Storage and Decide Whether ZFS FitsMatch guest disks, images, and backups to suitable storage.
  5. 13Create Your First Proxmox Virtual MachineBuild a small disposable Linux VM and verify its network and guest agent.
  6. 14Create a First Proxmox Container and Respect Its BoundariesRun a disposable LXC service while understanding shared-kernel risk.
  7. 15Schedule Proxmox Backups and Decide Whether You Need PBSPut guest backups on independent storage and choose a sustainable schedule.
  8. 16Prove Your Proxmox Backup With a Safe VM Restore DrillRestore a backup to a separate test identity and inspect the result.

operations

Operate and recover

Observe the lab, protect data and automate only the changes you can verify.

  1. 17Monitor your home lab and make alerts actionableBuild a small signal set, test delivery, and give every alert an owner and response.
  2. 18Back up your lab data and keep a recoverable copy elsewhereInventory data, schedule backups, protect an offsite copy, and prove a restore.
  3. 19Run your first local AI model on an existing Linux hostInstall a local runtime, run a small model, test its API, and keep it private.
  4. 20Private remote access to your home labReach one selected lab service remotely without opening its management port to the internet.
  5. 21Protect a lab with a UPS and graceful shutdownMatch load to a UPS, monitor its state, and rehearse a controlled shutdown.
  6. 22Write and rehearse a home lab incident runbookTurn an outage or security alert into a calm sequence of triage, recovery, and learning.
  7. 23Track configuration drift and keep a lab change logKnow what changed, why it changed, and how to undo it.
  8. 24Safely auto-restart one disposable serviceUse systemd's bounded restart policy, observe failure, and stop retry storms.
  9. 25Design a guarded graph loop for lab operationsConnect observation, diagnosis, approval, action, verification, and rollback without granting broad autonomy.