Dockge: Simple Docker Compose Management UI for Self-Hosters

TL;DR — Quick Summary

Deploy Dockge as a lightweight web UI for Docker Compose stack management. Create, start, stop, update, and monitor compose stacks without touching the terminal.

Why Dockge?

Managing Docker Compose stacks from SSH gets old fast. Dockge gives you:

Web-based compose editor — Write and edit docker-compose.yml in the browser.
One-click stack management — Start, stop, restart, update, delete.
Live container logs — Real-time log streaming per container.
Filesystem-based — Compose files live in /opt/stacks/, not a database.
Multi-host — Manage stacks across multiple Docker servers.

Prerequisites

Docker Engine 20+ with docker compose v2 plugin.
At least 128 MB RAM for Dockge itself.

Step 1: Deploy Dockge

mkdir -p /opt/stacks /opt/dockge
cd /opt/dockge

curl -o compose.yaml https://raw.githubusercontent.com/louislam/dockge/master/compose.yaml

docker compose up -d

Access at http://your-server:5001. Create your admin account.

Step 2: Create a New Stack

Click + Compose in the dashboard.
Name the stack (e.g., “homepage”).
Write or paste a docker-compose.yml:

version: "3"
services:
  homepage:
    image: ghcr.io/gethomepage/homepage:latest
    ports:
      - "3000:3000"
    volumes:
      - ./config:/app/config
    restart: always

Click Deploy — Dockge runs docker compose up -d for you.

Step 3: Manage Stacks

Action	What it does
Start	`docker compose up -d`
Stop	`docker compose down`
Restart	Stop + Start
Update	Pull latest images + recreate containers
Delete	Stop + remove compose file
Logs	Real-time container log streaming

Dockge vs Portainer

Feature	Dockge	Portainer CE
Focus	Docker Compose only	Full Docker + Kubernetes
Compose file storage	Filesystem (editable YAML)	Internal database
Resource usage	~50 MB RAM	~200+ MB RAM
Complexity	Minimal	Feature-heavy
Best for	Homelabs, simple setups	Enterprise, complex envs

Troubleshooting

Problem	Solution
”Port 5001 already in use”	Change the port in Dockge’s own `compose.yaml`
Stack shows “exited”	Click Logs to see container error output
Can’t edit compose file	Dockge locks the file while running; stop the stack first
Multi-host agent not connecting	Verify agent is running and firewall allows port 5001

Summary

5-minute setup — single docker compose command.
Compose files stay as editable YAML on your filesystem.
Perfect for homelabs and small teams managing 5-50 stacks.
Multi-host support via agents for distributed Docker setups.

Frequently Asked Questions

What is Dockge and how does it compare to Portainer?

Dockge is a lightweight Docker Compose management UI by the creator of Uptime Kuma. Unlike Portainer, which tries to manage every aspect of Docker (containers, images, networks, volumes, Kubernetes), Dockge focuses exclusively on docker-compose stacks. It stores compose files as standard YAML on your filesystem — no proprietary database. This makes it ideal for homelabbers who want a visual way to manage their stacks while keeping compose files editable and version-controllable.

Does Dockge replace the docker compose command?

Yes and no. Dockge uses docker compose under the hood. Every action you take in the UI (create, start, stop, update) runs the equivalent docker compose command. You can still run docker compose from the terminal alongside Dockge — they operate on the same YAML files.

Can Dockge manage stacks on multiple Docker hosts?

Yes. Dockge supports agents — you install a Dockge agent on each remote Docker host and connect them to your main Dockge instance. You can then manage all stacks across all hosts from one dashboard.

How do I update container images in Dockge?

Click on a stack, then click the Update button. Dockge pulls the latest images and recreates the containers. You can also enable auto-update checking to get notified when new images are available.