Build a home lab with the computer you already have

The first thing almost every mentee asks me is what they need to buy. The honest answer is nothing. The laptop you're reading this on can teach you most of what a first-year systems administrator knows, and it can do it this weekend.

A "home lab" sounds like it involves a rack, blinking lights, and a power bill. It doesn't. A lab is just a place where you're allowed to break things. That's the whole definition. Everything below is about creating that place on hardware you already own.

Start with virtual machines

A virtual machine is a computer running inside your computer. It has its own operating system, its own disk, and its own network connection, and when you destroy it, nothing on your real machine is affected. This is the single most important tool for learning IT, and it is free.

Install VirtualBox or VMware Workstation Player, then download an Ubuntu Server ISO. Give the VM two gigabytes of memory and twenty gigabytes of disk. Install it without a graphical desktop — you want the black screen with the blinking cursor, because that's what real servers look like.

The moment you stop being afraid of a terminal is the moment your learning speeds up about fivefold.

Give yourself something to actually run

An empty server teaches you nothing. Pick a service and stand it up properly, including the parts that are boring:

• A web server. Install nginx, serve a page, then get HTTPS working with a self-signed certificate. You will learn more about how the web works in one afternoon of certificate errors than in a month of tutorials.
• A file share. Set up Samba so your host machine can see a folder on the VM. Then break the permissions on purpose and fix them.
• A DNS resolver. Pi-hole is the classic choice. It's genuinely useful at home and it forces you to understand what DNS is doing.
• A second VM. Now you have a network. Make the two machines talk. Make one refuse to talk to the other with a firewall rule, then work out why.

Snapshot before you experiment

Every virtualisation tool lets you take a snapshot — a saved state you can roll back to in seconds. Take one before every risky change. This turns the terrifying question "what if I break it?" into a shrug, and that psychological shift matters more than any technical skill on this page.

Write down what you did

Keep a plain text file. Every time you get something working, paste in the commands that worked and one sentence about what went wrong first. Six months from now this file is the most valuable thing you own: it's your notes, your portfolio, and half your interview answers.

2026-07-12  nginx on ubuntu-vm-01
              sudo apt install nginx
              sudo ufw allow 'Nginx Full'
              # site was 403 until I fixed ownership:
              sudo chown -R www-data:www-data /var/www/html

When to spend money

Eventually you'll want hardware that runs all the time, and at that point a used mini PC or an old office desktop is worth roughly what you'd spend on a couple of takeaways. But get there because your lab outgrew your laptop, not because a video told you a proper lab needs three nodes. It doesn't.

If you want a hand setting any of this up, that's exactly the kind of thing our mentors do on a first session.