For: anyone with a home server from the first guide in this series. Time: 45 minutes. Difficulty: medium, but you only copy and paste once.
What is Docker?
Docker runs each app in its own sealed box, called a container. The box holds the app and everything it needs. That means:
- Apps don't clash with each other.
- Installing an app is one command, and removing it leaves no mess.
- Updating is "get the new box, swap it in".
Before you start
- A home server with Ubuntu Server or Debian, reached over SSH.
- Docker installed. Use the current instructions on docs.docker.com for your system, including the Compose plugin.
Check it works:
docker --version
docker compose version
Step 1: Make a home for your apps
Keep every app in its own folder, so it's easy to back up and tidy.
mkdir -p ~/apps/uptime-kuma
cd ~/apps/uptime-kuma
Step 2: Write a compose file
A compose file is a short text file describing the app. Create one with nano compose.yaml and paste this in:
services:
uptime-kuma:
image: louislam/uptime-kuma:2
container_name: uptime-kuma
restart: unless-stopped
ports:
- "3001:3001"
volumes:
- ./data:/app/data
Save with Ctrl+O, Enter, then exit with Ctrl+X. Spaces matter in this file, so copy it exactly.
What it says: use this app, restart it if the server reboots, make it available on port 3001, and keep its data in a folder next to the file.
Step 3: Start it
sudo docker compose up -d
The -d means "in the background". The first run downloads the app, which takes a minute.
Step 4: Open it
On a computer on your home network, go to http://SERVER-ADDRESS:3001. Create the admin account with a long, unique password. Then add a monitor for something you care about, like your router's address, so it tells you when it stops answering.
Step 5: Look after it
- See what's running:
sudo docker ps - Read an app's log:
sudo docker logs uptime-kuma - Stop it:
sudo docker compose down(your data stays in the folder) - Update it:
sudo docker compose pullthensudo docker compose up -d
The skull-dog says: Docker has a sneaky habit. When you publish a port, it can slip past your firewall rules. So only publish ports you mean to, and never forward them from your router to the internet. Keep it all inside your home, and use a private tunnel when you're out.
Choosing the next app
Good first picks for a home server:
- Uptime Kuma: tells you when something is down.
- Pi-hole or AdGuard Home: blocks adverts and trackers for the whole house.
- Jellyfin: streams your own films and music.
- Vaultwarden or similar: a self-hosted password vault (only if you're ready to look after it and back it up well).
Staying safe with apps
- Use apps from their official project page or Docker image, not a random blog's copy.
- Read the app's own install instructions before pasting anything.
- Pin a version when the project recommends it, rather than always grabbing "latest".
- Don't put secrets, like passwords, in a file you share publicly.
- Back up each app's folder. See the 3-2-1 rule.
Quick checklist
Common beginner mistakes
- Wrong spacing in the compose file. Copy exactly, and don't use tabs.
- Forgetting the data folder. Without it, the app forgets everything when it updates.
- Installing five apps at once. Add one at a time.
- Never updating. Put a reminder in your diary, or follow the monthly check.