You’ve got a few Docker containers running, everything’s working, and then it hits you: restarting them after a reboot means typing the same docker run commands over and over, remembering every flag, every port, every volume mount. There’s a better way, and it’s called Docker Compose. Setting up a docker compose home server is how homelabbers go from “I have containers” to “I have an actual system.”
Docker Compose lets you define your entire service stack in a single YAML file — every container, every network, every volume, all in one place. One command starts everything. One command tears it down. When your server reboots, everything comes back automatically. If you’re running more than two containers on your home server, this is the tool that makes it manageable.
What Is a Docker Compose Home Server Setup?
A docker compose home server is simply a machine running Docker where all your services are defined and managed using Compose files (compose.yaml). Instead of manually running each container with long docker run commands, you write a YAML file that describes every service, and Docker handles the rest.
The key benefits: reproducibility (your entire stack is documented in a text file you can back up), automatic restart policies (containers come back after reboots), dependency management (service B won’t start until service A is ready), and shared networking (containers in the same Compose file can talk to each other by service name, no IP address juggling required).
Step 1: Install Docker and Compose
On Ubuntu or Debian (which is what most homelab mini PCs run), install both with:
curl -fsSL https://get.docker.com | sh
That script installs Docker Engine and Docker Compose v2. Verify it worked: docker --version and docker compose version. Then add your user to the Docker group so you don’t need sudo every time: sudo usermod -aG docker $USER (log out and back in after).
Step 2: Understand the Compose File Structure
Here’s a minimal compose.yaml running Pi-hole:
services:
pihole:
image: pihole/pihole:latest
container_name: pihole
restart: unless-stopped
ports:
- "53:53/tcp"
- "53:53/udp"
- "8080:80"
environment:
WEBPASSWORD: "your-password-here"
volumes:
- ./pihole/etc-pihole:/etc/pihole
- ./pihole/etc-dnsmasq.d:/etc/dnsmasq.d
Three things to understand: restart: unless-stopped means the container auto-starts on reboot. volumes map folders on your host into the container — this is how data survives container restarts. ports map host ports to container ports in HOST:CONTAINER format.
Step 3: Run Your Stack
Save your compose.yaml in a folder (e.g., ~/homelab/pihole/), navigate there, and run:
docker compose up -d
The -d flag runs it detached (in the background). That’s it. Your services are running. To check status: docker compose ps. To see logs: docker compose logs -f. To stop everything: docker compose down.
Step 4: Build a Multi-Service Stack
The real power of Docker Compose comes when you combine services. Here’s a starter stack combining Pi-hole for DNS blocking and Vaultwarden for password management in a single file:
services:
pihole:
image: pihole/pihole:latest
restart: unless-stopped
ports:
- "53:53/tcp"
- "53:53/udp"
- "8080:80"
environment:
WEBPASSWORD: "changeme"
volumes:
- ./pihole/etc-pihole:/etc/pihole
vaultwarden:
image: vaultwarden/server:latest
restart: unless-stopped
ports:
- "8081:80"
volumes:
- ./vaultwarden/data:/data
Run docker compose up -d from that folder and both services start together. They share the same network by default, so they can communicate with each other by service name if needed.
The Hardware That Makes This Work
A solid docker compose home server needs reliable, always-on hardware. The Beelink EQ14 is the current sweet spot — Intel N150, 16GB RAM, 1TB NVMe, dual 2.5G LAN, and it idles at about 6–8W. That’s efficient enough to run 24/7 without adding meaningfully to your electricity bill, and capable enough to handle 10+ containers without breaking a sweat.
Pair it with an APC Back-UPS 600VA and your docker compose home server will survive power outages gracefully instead of corrupting databases mid-write — something you’ll be very glad about the first time the power flickers.
- 💡【Compact Size & Blazing Smooth Performance】The Beelink EQ14 mini pc packs an Intel Twin Lake N150 (4C/4T, max 3.6GHz) and pre-installed W 11 Home, delivering snappy performance for daily tasks, this Beelink mini desktop computer saves desk space, ideal for light office work. Effortlessly handle Zoom/Skype meetings, run Office/PS, surf the web and stream videos simultaneously. Perfect for office, online education, home entertainment and industrial use
- 💡【Storage Expansion】The Beelink EQ14 mini pc comes with 16GB DDR4 3200MHz RAM (single-channel, max 16GB) and a 1TB PCIe 3.0 SSD. It features dual M.2 slots: one M.2 SATA3 2280 and one M.2 PCIe 3.0 x1 (NVMe), supporting up to 8TB total internal storage (retail unit includes NVMe SSD). High-speed storage ensures smooth multitasking and fast data access
- 💡【 Intel Graphics & Dual HDMI Output】 The Beelink EQ14 mini pc features Intel Graphics (24EUs, 1000MHz) that supports crisp 4K video playback and smooth web surfing. Its dual HDMI ports let you connect two monitors simultaneously, boosting multitasking efficiency for office work, streaming, and more.
- 💡【Versatile I/O & Wireless Connectivity】The Beelink EQ14 mini pc boasts rich I/O ports: 2*HDMI ports, 2*2.5G LAN ports, 3*USB 3.2 ports, 1*USB 2.0 ports, 1*type-c port(data). It supports dual 4K displays via HDMI. Built-in WiFi6 (802.11ax, AX101, dual-band 2.4/5GHz) and BT5.2 ensure stable signals with strong anti-interference.
- 💡【Reliable Lifetime Service】We have been devoting to the production and R&D of Mini PC. Please feel free to contact us if you have any questions. We offer lifetime technical support, 3-year worry-free warranty, and 24 hours customer service.
- KEEP YOUR COMPUTER, WI-FI AND ROUTER RUNNING THROUGH POWER OUTAGES: Supplies short‑term battery power during outages to maintain internet connectivity and allow safe shutdown of computer during power interruptions.
- POWER PROBLEMS DON'T ONLY HAPPEN DURING STORMS — 23 minutes of runtime (at 100W load) guards against outages, while surge protection shields connected devices from unexpected power events that happen even on a normal day
- PROTECT EVERYTHING ON YOUR DESK - 5 well-spaced outlets with full battery backup and surge protection, plus 2 surge-only outlets for less critical gear
- PHONE CHARGER - Keep your phone charged even when the power's out. The built-in 1.5A USB port works during outages
- EASY BATTERY REPLACEMENT KEEPS COSTS LOW — swap the internal battery in minutes when it ages out, no need to replace the whole unit (APC replacement battery APCRBC154, sold separately)
The Takeaway: Docker Compose Home Server Is How You Graduate to a Real Homelab
Running a docker compose home server transforms your setup from a collection of containers you manage manually into a system that manages itself. One YAML file, one command, everything running and auto-restarting after every reboot. That’s the whole upgrade.
Start with one service in a Compose file, get comfortable with the format, then add more. Once you’re running four or five services this way, you’ll wonder how you ever did it with raw docker run commands. If you want to go deeper into virtualization, check out the Proxmox beginner setup guide — Proxmox and Docker Compose work beautifully together for more complex homelab setups.
What services are you planning to run? Drop them in the comments — I’d love to see what people are building.