Proxmox Home Server Setup for Your First Virtual Machines
You have one spare mini PC and five services you want to run, and every guide seems to assume you already know what a bridge, a storage pool and an LXC container are.

You have one spare mini PC and five services you want to run, and every guide seems to assume you already know what a bridge, a storage pool and an LXC container are. Setting up a Proxmox home server fixes that mess by letting one box run several isolated machines, but only if the first hour of setup goes right.
This guide walks through the choices that matter on a small machine: what hardware is enough, how to install without wiping the wrong disk, how to split work between containers and virtual machines, and which defaults to change before you put anything you care about on it.
What a Proxmox home server actually gives you
Proxmox VE is a free, Debian based hypervisor with a web interface. Once it is installed you stop thinking about the physical box and start thinking about guests. A Pi-hole can live in one container, a media server in another, and a test Ubuntu VM can be created, broken and deleted without touching either.
The real win is snapshots. Before you upgrade a guest, you take a snapshot in about two seconds. If the upgrade goes wrong, you roll back and the service is running again before anyone in the house notices. That single habit has saved me more evenings than any monitoring tool.
What it does not give you is free performance. Every guest shares the same CPU, RAM and disks. A machine that struggled to run three Docker containers on bare metal will not feel faster under a hypervisor.
Hardware that is enough for a first build
You do not need a rack server. For a household running five to eight light services, this is a comfortable starting point:
| Part | Minimum that works | What I would buy |
|---|---|---|
| CPU | 4 cores with VT-x or AMD-V | Intel N100 or a used 8th gen i5 |
| RAM | 8 GB | 16 to 32 GB |
| Boot and guest disk | 256 GB SSD | 500 GB to 1 TB NVMe |
| Network | 1 Gbps wired | Intel NIC, wired, never Wi-Fi |
RAM is the limit you hit first. Each small LXC container wants 256 to 512 MB, and a Windows VM wants 4 GB before it does anything useful. A used business mini PC with 16 GB costs around 120 to 180 dollars and idles at 8 to 12 watts, which is worth checking against your own tariff using our home server power cost numbers.
Installing Proxmox step by step
- Enable virtualization (VT-x or SVM) in the BIOS. Also turn on "restore on AC power loss" so the box comes back after an outage.
- Download the Proxmox VE ISO and write it to a USB stick with a tool such as Rufus or balenaEtcher.
- Boot from the stick and choose the graphical installer. On the disk screen, unplug any data drives first. Proxmox will happily format the wrong disk if you click too fast.
- For a single SSD, pick ext4. Choose ZFS only if you have two matching disks for a mirror and at least 16 GB of RAM.
- Give the host a static IP outside your router's DHCP range, for example 192.168.1.5, and a real hostname like pve1.home.
- After reboot, open https://192.168.1.5:8006 in a browser and log in as root.
The whole install takes about ten minutes. The next thirty minutes are where most people skip steps.
First changes after the install
The free version ships pointing at the enterprise update repository, which needs a paid key. In the web interface, go to the node, then Updates, then Repositories. Disable the enterprise entries and add the "No-Subscription" repository. Then run updates from the shell:
apt update followed by apt full-upgrade, then reboot.
Next, create a normal admin user, enable two factor login for it under Datacenter and Permissions, and stop using root for daily work. If you plan to reach the interface from outside your network, read our checklist on what to check before exposing a home server online first. Port 8006 should never be forwarded on your router.
Containers or virtual machines for each service
Proxmox runs two kinds of guests, and picking the right one saves a lot of RAM.
- LXC containers share the host kernel. They boot in two seconds, use very little memory and suit Linux services like Pi-hole, a reverse proxy, a small database or a file sync tool.
- Virtual machines run their own kernel. Use them for anything that is not Linux, anything that needs a custom kernel module, or anything you want strongly isolated, such as a guest exposed to the internet.
A practical split on a 16 GB box: four containers at 512 MB each, one Ubuntu VM at 4 GB running Docker, and 6 GB left for the host and headroom. Leave at least 2 GB unassigned. Overcommitting RAM works until the night everything gets busy at once, and then the kernel starts killing guests.
The advice I would ignore: put everything in one big Docker VM
A popular suggestion is to skip containers entirely and run one large VM with every service inside Docker. The argument is simplicity: one machine to back up, one place to run compose files.
I disagree for a home setup, and the reason is blast radius. When that single VM has a broken update or a full disk, every service goes down together, including the DNS your family depends on. Snapshots also become blunt. Rolling back to fix your media server also rolls back the password vault you edited an hour ago.
Keep critical household services, like DNS and the reverse proxy, in their own small containers. Put the experimental stuff in a Docker VM. You get cheap rollbacks where they matter and a sandbox where you want one.
Backups and storage you should set up on day one
Snapshots are not backups. They live on the same disk, so a dead SSD takes the snapshots with it. Proxmox includes a scheduled backup job under Datacenter, then Backup. Point it at a second disk, a NAS share or a Proxmox Backup Server instance, and set it to run nightly at 03:00 with a retention of seven daily and four weekly copies.
Use "snapshot" mode so guests keep running during the job. A backup of six small guests usually finishes in under fifteen minutes and takes 20 to 40 GB with compression. Once a month, restore one guest to a new ID and boot it. A backup you have never restored is a hope, not a plan. Our piece on running a home backup server day to day covers the routine that keeps this honest.
Finally, set up email notifications under Datacenter so failed backup jobs actually reach you. A silent failure that runs for three months is the most common way home lab data gets lost.
Frequently asked questions
Is Proxmox free for home use?
Yes. Proxmox VE is open source and every feature works without a subscription. The paid plans add the stable enterprise repository and support, which a home user rarely needs. You will see a subscription reminder at login, which is cosmetic.
How much RAM does a Proxmox home server need?
Proxmox itself runs on about 1.5 to 2 GB. For a handful of containers, 8 GB is workable, but 16 GB gives you room for one or two virtual machines without constant juggling. If you want ZFS, budget roughly 1 GB extra per terabyte of storage for its cache.
Can I run Proxmox on a laptop or mini PC?
A mini PC is one of the best options because it is quiet and uses little power. A laptop works too, and its battery acts like a small UPS, but Wi-Fi is not supported well for bridged guests. Use a wired Ethernet port or a USB adapter with a known good chipset.
More in Self Hosting
Self Hosting
Dynamic DNS Setup to Reach Your Home Server by Name
The server at home is fine. The router is fine. What broke is the sentence you memorised two months ago, the one with four...
Self Hosting
Minecraft Server on a Mini PC: RAM, Flags and Backups
The server my friends play on is a fanless Intel N100 mini PC that cost $155, sits on a shelf behind the router, and has been...
Self Hosting
Updating Self Hosted Containers Without Breaking Them
Nothing on the server is broken, which is exactly why the Nextcloud container on mine spent fourteen months running an image I...