// GUIDE 08

Run your first apps with Docker

Home Lab Starter series · Part 2 of 5

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:

Before you start

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

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:

Staying safe with apps

Quick checklist

Common beginner mistakes