Set up your first home lab

A home lab is a small pile of ordinary computer hardware in your house, running real services, that you use to learn on.

It is the single most effective way to learn IT, and it is how most working professionals actually learned. This is how to start one.

Why bother

You cannot learn infrastructure from a book, for the same reason you cannot learn to drive from one.

Reading about virtual machines teaches you the words. Running six of them, watching one fall over, and working out why teaches you the subject. The difference shows up immediately in an interview.

It also solves the problem every entry-level candidate faces: every job advertisement asks for experience, and nobody will give you any. A home lab is experience you can give yourself. Nobody has to hire you first.

The lab is not a study aid. It is the thing you will talk about in the interview that gets you the job.

What you need

Far less than people think. Resist the urge to buy a rack of servers.

A computer, ideally with 16GB of memory. A retired office desktop is perfect. Businesses replace these on a cycle and they turn up second-hand constantly for under $150, sometimes free if you ask around. An old gaming PC works. A laptop works, though desktops are easier to add drives to.

Some storage. Whatever is in it, plus a second drive if you can.

Your existing home network to start with. A cheap managed switch later, once you want to do VLANs properly, is around $50 to $100.

A USB stick for installing things.

That is genuinely it. Total realistic outlay: $0 to $200.

What to build first

Do these in order. Each one is useful on its own, and each teaches something the next one needs.

Step 1: Install a hypervisor

A hypervisor turns one physical machine into many virtual ones. This is the moment your computer stops being a computer and becomes infrastructure.

Proxmox is the right choice for a first lab. It is free, open source, has a web interface you reach from any browser in the house, and it is close enough to what businesses use that the skills transfer directly.

Install it, get to the web interface, and you have already done the hardest part.

Step 2: Create your first virtual machines

Make two. Put Ubuntu Server on one and Windows on the other.

You now have two computers that did not exist an hour ago, that you can break freely, and that you can delete and recreate in ninety seconds when you do.

That last part is the point. The freedom to destroy things is what makes a lab a lab.

Step 3: Learn the command line

On that Ubuntu machine, with no graphical interface to fall back on.

This is the part people avoid and it is the part that matters most. Every server you will ever touch professionally is administered this way. Learn to move around, edit files, install software, read logs and manage services.

It feels hostile for about a fortnight and then it feels faster than clicking.

Step 4: Run something the household uses

This is where it gets genuinely valuable, and it is the step most people skip.

Run a service that other people in the house depend on. A media server. A network-wide ad blocker like Pi-hole. Shared file storage.

The moment somebody else relies on it, you have real uptime pressure. You cannot reboot it whenever you like. You have to plan changes. You will get complaints. That is exactly the experience you are trying to manufacture, and it cannot be simulated.

Step 5: Build a real network

Segment the lab away from the family computers. Learn addressing properly. Set up your own DNS. Write firewall rules that actually block something and understand why.

Networking is the subject that separates hobbyists from professionals, and it is the one most self-taught people skip because it is less immediately rewarding. Do not skip it.

Step 6: Break it deliberately, then fix it

Pull a disk out while it is running. Corrupt a configuration file. Fill the drive. Change an IP address and see everything stop.

Then diagnose it properly, with logs rather than guessing, and fix it.

This is the actual skill. Everything up to here was setup.

Step 7: Write it down

Document what you built, why you chose it, and what went wrong. Keep it in a text file, a wiki, or a repository.

Two reasons. Documenting is a professional habit that separates people who get promoted from people who do not. And it becomes your portfolio: something concrete to show an interviewer.

What to avoid at the start

Buying enterprise server hardware. Loud, power-hungry, and unnecessary. Your electricity bill and your family will both object.

Buying anything before you have run out of road with what you have. Every purchase should be triggered by a specific thing you cannot currently do.

Following a tutorial without understanding it. Copying commands teaches you nothing. If you do not know what a step does, stop and find out.

Only touching things that work. The learning is in the breakage.

About the power bill

A single small desktop running continuously costs a few dollars a week. Roughly a lamp.

Old enterprise servers are a different matter entirely, which is another reason not to start with one.

Doing it legally

Everything in your lab is your equipment on your network. Keep it that way.

Security is a legitimate and valuable thing to learn, and it is taught professionally by understanding how attacks work in order to defend against them. That learning happens inside your own lab, against your own machines, always.

Never against systems belonging to anybody else, including a school, an employer, or an open network you happened to find. That is the line between a career and a criminal record, and it is not a subtle one.

If you want a hand getting started

The first session is usually the hardest, because getting a hypervisor installed and a first virtual machine running involves a few decisions that are obvious afterwards and opaque beforehand.

That is exactly what the home lab sessions are for, and there is a Home Lab Bootcamp running on Saturdays for teenagers and career changers. You take the lab home with you.