Tag: docker

Yes, most desktop PCs from roughly 2012 onward can become a capable home server. The short version: back up anything on it you want to keep, flash Ubuntu Server to a USB stick, install it over the old operating system, turn on SSH, and change three BIOS settings so the machine behaves like a server instead of a desktop. The conversion itself takes about an hour. The two questions most guides skip are the ones that actually matter: is your specific PC worth converting, and what will running it 24/7 cost you in electricity? This guide answers both, with a cutoff table and real math.

If you are still deciding whether you need a server at all, start with the pillar guide to what a home server is and what people actually use one for, then come back here.

Is your PC too old? The cutoff table

Every guide says "any old PC will do." That is not true, and the difference is not subtle. Use your CPU's generation as the dividing line. On Intel chips you can read the generation straight off the model number: an i5-3470 is 3rd generation, an i5-8400 is 8th generation. On Windows, press Ctrl+Shift+Esc, open the Performance tab, and the CPU model is printed in the top right.

The 60-second "will it actually work" checklist

Before you spend an evening on this, check six things:

1. 64-bit CPU. Anything from the table's usable rows qualifies. Ubuntu no longer ships for 32-bit processors.
2. At least 4 GB of RAM. 4 GB runs a file server plus an ad blocker fine. 8 GB is comfortable for a media server and several apps. Old DDR3 sticks are cheap secondhand if you want to upgrade.
3. A wired Ethernet port. Servers should not live on Wi-Fi. If the PC will sit far from your router, plan for a cable anyway.
4. A working disk, or a plan to replace it. A drive that has already survived years of desktop duty is the most likely part to fail. A small SSD for the operating system is the single best upgrade you can make.
5. It can run all day without overheating. Blow the dust out, make sure the fans spin, and let it idle for a few hours before trusting it.
6. An idle power draw you can live with. This is the dealbreaker nobody checks. The electricity section below shows you the math.

One more point in favor of converting: if the machine is stuck on Windows 10, which Microsoft stopped supporting on October 14, 2025, it is no longer safe as an internet-facing Windows PC anyway. A supported Linux server OS gives that hardware a secure second life.

Step 1: Back up, then accept the wipe

The install below erases the entire drive. Before you start:

• Copy documents, photos, and browser bookmarks to an external drive or cloud storage. Check the Desktop, Downloads, and Documents folders; that is where 90 percent of forgotten files hide.
• If any paid software on the machine has a license you might reuse (a game library, an office suite), sign out or deactivate it first.
• Do not try to keep Windows "just in case" on the same disk. Dual-booting a server defeats the point of a machine that runs 24/7, and it doubles the ways an update can break your boot process.

Step 2: Install Ubuntu Server, step by step

I recommend Ubuntu Server for a first conversion because it is free, it runs without a graphical desktop (so old hardware feels fast), and the current long-term support release, Ubuntu Server 26.04 LTS, receives updates from Canonical until 2031. Your server OS decision is one you make once; five years of guaranteed patches is the right default.

2.1 Download the installer

On your everyday computer, download the Ubuntu Server LTS ISO file from ubuntu.com. It is a few gigabytes.

2.2 Flash it to a USB stick

You need a USB stick of 4 GB or larger (it will be erased). Use a flashing tool such as Rufus (Windows) or balenaEtcher (Windows, Mac, Linux): pick the ISO, pick the stick, click start, wait a few minutes.

2.3 Boot the old PC from the USB stick

Plug the stick into the old PC and power it on while tapping the boot-menu key. It varies by manufacturer: F12, F11, F10, F8, Esc, and Del are the common ones, and the correct key usually flashes on screen for a second at power-on. Choose the USB device from the menu.

2.4 Walk through the installer

The Ubuntu Server installer is text-based but simple. The choices that matter:

1. Language and keyboard: pick yours.
2. Network: the installer shows the IP address your router assigned. Write it down; you will need it in step 2.6.
3. Storage: choose "Use an entire disk." Confirm the wipe. Leave the default layout alone.
4. Profile: give the server a short hostname (something like homeserver), plus a username and a strong password. This account controls the machine; do not reuse a throwaway password.
5. SSH: check Install OpenSSH server. This is the one box you must not skip. SSH is how you will control the server from your normal computer, which is what lets it live in a closet with no monitor.
6. Featured snaps: skip them all. Install apps deliberately later, not from a checklist you have not researched.

Reboot when prompted and pull the USB stick out.

2.5 First login and updates

Log in at the server's own keyboard once with the username and password you created, then bring it fully up to date:

sudo apt update && sudo apt upgrade -y

2.6 Give it a permanent address

Your server needs an IP address that never changes, or nothing will reliably find it. The easiest method is not on the server at all: log in to your router's admin page, find "DHCP reservation" (sometimes "static lease" or "address reservation"), and pin the server's IP to its hardware address. Two minutes, no config files, and it survives reinstalls.

2.7 Go headless

From your everyday computer, open a terminal (PowerShell on Windows works) and connect:

ssh yourusername@192.168.1.50

Substitute your username and the reserved IP. Once that works, you can unplug the server's monitor and keyboard for good. That is the moment an old PC becomes a server.

Step 3: The three BIOS settings that make it a real server

This is the part nearly every guide skips, and it is the difference between a machine you babysit and one you forget about. Reboot the server, enter BIOS setup (usually Del or F2 at power-on), and set:

1. Restore on AC power loss: Power On. The setting goes by many names ("AC Back," "After Power Failure," "Restore AC Power Loss"). Default behavior after a power outage is to stay off, which means your server dies the first time the power blinks while you are away. Set it to power on and the machine restarts itself the moment electricity returns.
2. Boot without a keyboard. Some older boards halt with a "keyboard error" if nothing is plugged in. Look for "Halt On" or "Keyboard Error" and set it to ignore. Otherwise your headless server will sit at an error screen forever after its first unattended reboot.
3. Wake-on-LAN: Enabled. Optional but worth it. It lets you power the machine on remotely with a "magic packet" from another device, so you can shut the server down when you travel and wake it without touching it.

The electricity math nobody shows you

An old tower is free to acquire and not free to run. The formula is simple: watts at idle × 8.76 = kilowatt-hours per year for a machine that is on around the clock. The US average residential electricity rate was about 18.8 cents per kWh as of April 2026, per the US Energy Information Administration; the table below uses a round 18 cents. Check your own bill, because state rates vary enormously.

*These are typical ranges, not measurements of your machine. An inexpensive plug-in watt meter tells you your real number in ten seconds, and it is the most clarifying purchase in this whole project.

Read the table honestly: the oldest towers can cost more per year in electricity than the gap between "free old PC" and an entry-level mini PC. Run the comparison for your own machine: take its measured idle wattage, project the cost over two or three years at your local rate, and put that next to what an entry-level mini PC sells for where you live. Newer towers and laptops usually win the comparison; pre-2013 towers often lose it.

Three ways to shrink the number on any old PC: replace the boot hard drive with an SSD, unplug drives you are not using, and enable your CPU's power-saving states if the BIOS has them disabled.

When turning an old PC into a home server is a bad idea

I would rather talk you out of a bad conversion than have you sour on home servers entirely. Skip the old PC if:

• It predates 2009. Between the idle power draw and the RAM ceiling, you are paying yearly, in electricity, for hardware that cannot run much. Recycle it.
• It is your only computer. A converted server runs headless with no desktop. You need a separate everyday machine.
• It has to live where you sleep or work. Old towers have old fans. A machine in a bedroom or on a desk needs to be near-silent, and that usually means a laptop, a mini PC, or new fans you did not budget for.
• The math above clearly loses. A high-idle-wattage tower that will run 24/7 for years is a recurring bill dressed up as a free computer. Budget mini PCs exist precisely because of this trade-off, and their power savings compound every month.
• You want it to run your smart home or backups with zero drama from day one. Aging power supplies and drives fail more often than new ones. You can absolutely build reliably on old hardware, but only if you also set up automated backups, which is non-negotiable either way.

None of this means the old PC route is wrong in general. For learning, and for any machine from the table's middle rows, it is the best value in home computing. The pillar guide covers how to decide what your home server is actually for before you commit hardware to it.

What to run first

Resist installing ten things on night one. Pick a single app, run it for a week, then add the next. Good first candidates and how to choose between them are covered in our roundup of the best self-hosted apps for beginners; network-wide ad blocking and a file-sync service are the classic starters because you feel the benefit within a day.

One warning as soon as you want to reach the server from outside your house: do not forward ports on your router to expose it to the internet. The beginner-safe route is a private mesh network, which we walk through in how to access your home server from anywhere with Tailscale.

FAQ

Can I still use the PC as a normal computer after converting it?

Not practically. Ubuntu Server has no desktop interface, and the value of a server comes from it running untouched 24/7. If you still need the machine as a desktop, it is not ready to be your server.

Can I use an old laptop instead of a desktop?

Yes, and for many people it is the better donor: laptops idle at a fraction of a tower's wattage, run quietly, and the battery acts as a built-in backup power supply during brief outages. Configure the OS not to sleep when the lid closes, and make sure the closed lid does not block its vents.

Do I have to use Linux, or can I keep Windows?

You can run a server on Windows, but on old hardware it is the worse tool: it spends more RAM and CPU on itself, and most self-hosted apps are built Linux-first. There is also the support problem, since Windows 10 stopped receiving security updates in October 2025 and many older PCs cannot officially upgrade to Windows 11. Ubuntu Server is free and supported into 2031.

How much RAM does an old PC need to work as a home server?

4 GB is a workable floor for file serving, backups, and ad blocking. 8 GB is comfortable for a media server plus several apps. 16 GB only matters once you are running many services at once, which is not a first-month problem.

Will running an old PC 24/7 wear it out?

Continuous running is gentler on components than daily power cycling, but old drives are still the weak point. Assume the drive can fail, keep automated backups of anything you care about, and the rest of the machine will usually soldier on for years.

To set up a home server for beginners, take a computer you already own (an old laptop or desktop works fine), install a free server operating system like Ubuntu Server, connect to it from your main computer over your home network, and use Docker to run one app, such as a photo backup or a personal cloud drive. A basic setup takes about an hour. You do not need to buy special hardware, open your router to the internet, or set up RAID to begin. The trick is to pick one job for the server first, get that working, and grow from there.

Most guides get the order wrong. They hand you a parts list and a page of network settings before you know what the machine is even for. This one starts with the decision, uses hardware you probably already have, and is honest about the parts nobody mentions: what it costs to run, what breaks, and when a home server is not worth the trouble.

What a home server actually is

A home server is just a computer that stays on and does a job for the other devices in your house. That is the whole idea. Instead of your photos living on Google's computers and your files living on Dropbox's computers, they live on a machine in your home that you control. Your phone, your laptop, and your TV connect to it over your own Wi-Fi. It is a private cloud that you own outright, with no monthly bill and no company reading your data.

It does not have to be a rack of blinking machines. A ten-year-old laptop with the lid closed in a cupboard is a real home server. What makes it a "server" is not the hardware, it is the fact that it runs quietly in the background and answers requests from your other devices.

Decide what your home server is for first

Before you touch any hardware, answer one question: what is the first job? Pick a single, concrete use. You can add more later, but starting with everything at once is how beginners give up. Here are the three most common starting points.

• Your own cloud drive (file backup). Replace Dropbox or Google Drive with your own storage that your phone and laptops back up to automatically. The usual apps for this are Nextcloud or Seafile.
• Your own photo library (a Google Photos alternative). Back up every photo and video from your phone to your own server, with albums, search, and sharing. The popular self-hosted app here is Immich.
• Your own media library. Stream your movies, shows, and music to any screen in the house. The common apps are Jellyfin (fully free) or Plex.

Pick one. If you cannot decide, choose the photo library or the cloud drive, because those solve a problem you already feel every time your phone says "storage full." Media streaming is fun but it is a bigger first project.

A home server can also run smart-home control (Home Assistant), ad-blocking for your whole network (Pi-hole), and dozens of other tools. Ignore all of that for now. One job first.

What you need to set up a home server (and what you don't)

Here is the good news that the shopping-list guides bury: the hardware you already own is almost certainly enough to start. A home server for one or two apps is not a demanding machine.

Minimum to begin: any 64-bit computer from roughly the last decade, with about 4 GB of RAM and a working drive. Ubuntu Server, the operating system we will use, officially installs with about 1.5 GB of RAM and runs comfortably on 2 GB or more, so an old laptop or office desktop clears the bar with room to spare. You also need a way to plug it into your router. A wired network cable is more reliable than Wi-Fi for something that stays on, but Wi-Fi works.

Use this table to match what you already have to the route that fits:

When your hardware is not enough: if you want to stream 4K video to several screens at once, or store a very large media library, you will eventually want more RAM and more disk space. That is a later problem. It is not a reason to spend money on day one. Start on what you have, learn how it works, and let the real limits tell you what to upgrade. For a deeper walkthrough of picking and prepping a machine, see our guide on how to turn an old PC into a home server, which is this hardware chapter expanded.

A note on how this guide was written

The steps below follow the current official Ubuntu Server and Docker documentation and the standard beginner install path. The commands were checked against the current published docs at the time of writing. This is a documented walkthrough, not a review of a specific test rig, so your exact screens and version numbers may differ a little by hardware and by which version you download. Where a step depends on your own machine (its IP address, its power draw), the guide shows you how to find your number rather than inventing one.

Step by step: install the operating system

We will install Ubuntu Server, a free Linux operating system built to run in the background with no screen attached. It is the most documented beginner-friendly choice, which matters a lot the first time something goes wrong and you need to search for an answer.

1. Download the installer. On your normal computer, go to ubuntu.com and download the latest Ubuntu Server LTS ISO file. "LTS" means long-term support, which is what you want for a machine that just runs.
2. Write it to a USB stick. Use a free tool like Balena Etcher or Rufus to write the ISO to a USB drive (8 GB or larger). This erases the USB stick, so use a spare.
3. Boot the old computer from the USB stick. Plug the stick into the machine that will become your server, turn it on, and press the key that opens the boot menu (often F12, F2, Esc, or Del, depending on the make). Choose the USB drive.
4. Follow the installer. Accept the defaults for most screens. When it asks about storage, the guided "use entire disk" option is correct for a machine you are dedicating to this. Set your language, create a username and a strong password, and write them down.
5. Turn on remote access. This is the one step beginners skip and regret. When the installer offers to "Install OpenSSH server," check that box. It is what lets you control the server from your normal computer instead of hunching over the old one.
6. Finish and reboot. Remove the USB stick when told, let it restart, and log in once on the machine itself with the username and password you set.
7. Find the server's address. On the server, type ip a and press Enter. Look for an address that starts with 192.168. or 10.. That is your server's local IP address on your home network. Write it down. You can now walk away from this machine for good.

If you would rather use a storage-focused operating system with a friendly web screen instead of the command line, TrueNAS and Unraid are the usual alternatives. They are heavier first projects, so this guide sticks with Ubuntu Server.

First contact: connect to your server from another device

Now you control the server from the comfortable computer you already use. This is where it starts to feel real.

• On Mac or Linux: open the Terminal app and type ssh yourusername@192.168.x.x, replacing that with your username and the IP address you wrote down. Press Enter.
• On Windows: open PowerShell and use the same ssh yourusername@192.168.x.x command (modern Windows includes SSH), or install the free PuTTY app and enter the IP there.

The first time, it asks you to confirm a fingerprint. Type yes. Enter your password (the screen will not show the characters as you type, which is normal). You are now logged into your server from across the room. Everything from here happens through this window.

Good first habit: update the system before anything else. Run these two commands:

sudo apt update
sudo apt upgrade

Enter your password when asked, confirm, and let it finish. You have now done the single most important piece of ongoing maintenance a server needs.

Install your first app with Docker

Here is the part that used to be hard and is now easy: running apps. We use Docker, a tool that packages each app with everything it needs so you do not spend an evening fighting dependencies. You install Docker once, then most self-hosted apps become a short, copy-paste affair.

Install Docker with the official convenience script:

curl -fsSL https://get.docker.com | sh

Test that it works:

sudo docker run hello-world

If you see a friendly "Hello from Docker!" message, Docker is running. That message is the whole point: you just pulled an app from the internet and ran it in an isolated container without installing anything by hand.

From here, real apps follow the same pattern, usually written as a small "Docker Compose" file (a plain text recipe that lists the app and its settings). You run one command, docker compose up -d, and the app starts and stays running. For a beginner's very first real app, the photo library is the most satisfying, because it solves the "phone storage full" problem the same day. Follow our step-by-step guide to self-host Immich, a private Google Photos alternative, which walks the Compose file line by line. When you want ideas for what to add next, our roundup of the best self-hosted apps for beginners lists the ones that are genuinely easy to run.

One job, running, on hardware you already owned. That is a working home server.

What a home server actually costs to run

This is the section other guides leave out, and it is the one that decides whether you keep the thing plugged in. A home server is cheap, but it is not free.

Electricity. The server is on all the time, so its power draw matters more than its price. An old desktop tower often idles somewhere around 50 to 100 watts, and older machines or ones with a dedicated graphics card can pull well over 100 watts even when doing nothing. A laptop or a Raspberry Pi is far kinder, often under 20 watts. Left on continuously, a typical desktop can use in the region of 600 kilowatt-hours a year. To get your real number, do not guess: measure it with an inexpensive plug-in power meter, then multiply the watts by 24 hours and 365 days, divide by 1,000, and multiply by your local electricity rate. That is your true yearly cost. This is exactly why the table earlier said not to draft a power-hungry gaming PC into 24/7 duty: the electricity can quietly cost more than the cloud subscription you were trying to escape.

Noise and heat. An old tower with spinning fans and hard drives is not silent. If it lives in a bedroom, you will hear it. A laptop or a small machine with an SSD is close to silent. Pick where it lives with your ears in mind.

Your time. The honest cost is maintenance. Setup is about an hour. After that, expect to spend a little time now and then running updates and, eventually, dealing with something that broke. Drives fail. Apps get updates that change a setting. It is not a heavy burden, but it is not zero, and it never fully goes away.

When NOT to bother

A home server is not the right answer for everyone, and pretending otherwise would waste your weekend.

• If you only need a couple of folders backed up and you are happy paying a small cloud fee, a server is more machine than the problem needs.
• If nobody in the house can tolerate occasional fiddling, think twice before putting important family data on a server you will not maintain.
• If your electricity is expensive and your only spare machine is a power-hungry tower, the running cost may beat a subscription. A low-power Pi or a NAS changes that math.
• If you want genuinely zero fuss, a ready-made NAS appliance or a paid cloud service is a better fit than a DIY server, and there is no shame in that.

And the rule that saves people the most pain: a single home server is not a backup. If the only copy of your photos lives on it, one dead drive erases them. Keep a second copy somewhere else (another drive or a cloud account) for anything you cannot lose. A server holding the one and only copy of your memories is a risk, not a safety net.

What not to do yet

Beginners get into trouble by doing advanced things too early. On day one, deliberately skip all of this:

• Do not forward ports on your router or expose the server to the internet. This is the single most common beginner mistake and the fastest way to get attacked. Everything above works entirely on your home network, safely. When you do want to reach your server from outside the house, the safe way is not port forwarding. Use our guide to reach your home server safely with Tailscale, which creates a private connection with nothing opened to the public internet.
• Do not set up RAID on day one. RAID keeps a server running when a drive dies, but it is not a backup and it adds complexity you do not need yet. Get one app working first.
• Do not buy anything. No new drives, no rack, no fancy case, no "server grade" hardware. Use what you have until a real limit tells you otherwise.
• Do not chase a static public IP or a domain name yet. You need none of it to run apps on your own network.

Skipping these is not laziness. It is the correct order. Advanced setup is worth doing later, once the basics are second nature.

Where to go next

You now have a real home server doing one useful job. To grow it sensibly, pick your next step:

• Prepare or upgrade the machine properly with the turn an old PC into a home server guide.
• Solve the "phone storage full" problem for good by learning to self-host Immich.
• Add more tools from the best self-hosted apps for beginners.
• When you are ready to reach it from anywhere, do it the safe way with Tailscale.

Add one thing at a time. That is the entire secret to not getting overwhelmed.

FAQ

Can I use an old laptop as a home server?
Yes, and it is one of the best beginner choices. A laptop uses far less electricity than a desktop tower, runs quietly, and has a built-in battery that acts like a small backup power supply during brief outages. Install Ubuntu Server, then adjust its settings so it keeps running with the lid closed, and tuck it away near your router.

Does a home server need to run 24/7?
Only if the job needs it. If you want your phone to back up photos at any hour or stream media whenever you sit down, the server should stay on. If it only does a nightly task, you can schedule it to wake and sleep. Leaving it on is what drives the electricity cost, so match the uptime to what you actually use.

Will a home server slow down my internet?
For everything in this guide, no. The server talks to your phone and laptops over your local network, which does not touch your internet connection at all. It can use internet bandwidth if you later set it up to be reached from outside the house, but the basic setup here stays inside your home and leaves your browsing speed untouched.

Is Ubuntu Server or Windows better for a beginner home server?
Ubuntu Server is the better first choice for most people. It is free, it is built to run without a screen, and it has the largest pool of beginner guides and community answers, which matters the moment you get stuck. Windows can run a home server too, but it costs money, uses more resources, and has far less self-hosting documentation aimed at beginners.

How much does it cost to run a home server?
The main cost is electricity, and it depends entirely on the machine. A low-power laptop or Raspberry Pi might cost very little a year, while an old desktop left on all the time costs meaningfully more. Measure your machine's watt draw with a plug-in power meter, then multiply by the hours it runs and your local electricity rate. Beyond power, the real cost is a little of your time for updates and the occasional repair.