A fancy, easy-to-use and reactive self-hosted docker compose.yaml stack-oriented manager.
This repository is a fork of louislam/dockge.
This fork includes many extra integrations, requested features, UI changes, and active layout updates. NekoSuneVR intends to keep this branch updated, but it is best treated as an early-access branch because a lot of changes happen here first.
View Video: https://youtu.be/AWAlOQeNpgU?t=48
- 🧑💼 Manage your
compose.yamlfiles- Create/Edit/Start/Stop/Restart/Delete
- Update Docker Images
- ⌨️ Interactive Editor for
compose.yaml - 🦦 Interactive Web Terminal
- 🕷️ (1.4.0 🆕) Multiple agents support - You can manage multiple stacks from different Docker hosts in one single interface
- 🏪 Convert
docker run ...commands intocompose.yaml - 📙 File based structure - Dockge won't kidnap your compose files, they are stored on your drive as usual. You can interact with them using normal
docker composecommands
- 🚄 Reactive - Everything is just responsive. Progress (Pull/Up/Down) and terminal output are in real-time
- 🐣 Easy-to-use & fancy UI - If you love Uptime Kuma's UI/UX, you will love this one too
Requirements:
- Docker 20+ / Podman
- (Podman only) podman-docker (Debian:
apt install podman-docker) - OS:
- Major Linux distros that can run Docker/Podman such as:
- ✅ Ubuntu
- ✅ Debian (Bullseye or newer)
- ✅ Raspbian (Bullseye or newer)
- ✅ CentOS
- ✅ Fedora
- ✅ ArchLinux
- ❌ Debian/Raspbian Buster or lower is not supported
- ❌ Windows (Will be supported later)
- Major Linux distros that can run Docker/Podman such as:
- Arch: armv7, arm64, amd64 (a.k.a x86_64)
- Default Stacks Directory:
/opt/stacks - Default Port: 5001
# Create directories that store your stacks and stores Dockge's stack
mkdir -p /opt/stacks /opt/dockge
cd /opt/dockge
# Download the compose.yaml
curl https://raw.githubusercontent.com/louislam/dockge/master/compose.yaml --output compose.yaml
# Start the server
docker compose up -d
# If you are using docker-compose V1 or Podman
# docker-compose up -d
Dockge is now running on http://localhost:5001
If Dockge itself runs in a container, GPU detection only works when the Dockge container can see the host GPU information.
For Linux hosts:
- Intel / AMD: share
/dev/driand/sys/class/drm - NVIDIA: share
nvidia-smiif present, and mount/proc/driver/nvidiato a normal container path, not into/proc
Example additions for the dockge service:
services:
dockge:
volumes:
- /sys/class/drm:/sys/class/drm:ro
- /proc/driver/nvidia:/run/dockge-host/proc-driver-nvidia:ro
- /usr/bin/nvidia-smi:/usr/bin/nvidia-smi:ro
devices:
- /dev/dri:/dev/driNotes:
/dev/driis mainly useful for Intel and AMD GPUs, and some integrated GPUs./proc/driver/nvidiaandnvidia-smiare mainly useful for NVIDIA GPUs.- Do not bind-mount host
/proc/driver/nvidiainto container/proc/driver/nvidia; Docker rejects mounts inside container/proc. - Uncomment only the mounts that exist on your host. If a path does not exist, Docker may fail to start the container.
If you want to store your stacks in another directory, you can generate your compose.yaml file by using the following URL with custom query strings.
# Download your compose.yaml
curl "https://dockge.kuma.pet/compose.yaml?port=5001&stacksPath=/opt/stacks" --output compose.yaml
- port=
5001 - stacksPath=
/opt/stacks
Interactive compose.yaml generator is available on: https://dockge.kuma.pet
cd /opt/dockge
docker compose pull && docker compose up -dThis repo includes a local feature changelog at CHANGELOG.md for the custom additions made here.
- I have been using Portainer for some time, but for the stack management, I am sometimes not satisfied with it. For example, sometimes when I try to deploy a stack, the loading icon keeps spinning for a few minutes without progress. And sometimes error messages are not clear.
- Try to develop with ES Module + TypeScript
If you love this project, please consider giving it a ⭐.
https://github.com/louislam/dockge/issues
https://github.com/louislam/dockge/discussions
If you want to translate Dockge into your language, please read Translation Guide
Be sure to read the guide, as we don't accept all types of pull requests and don't want to waste your time.
"Dockge" is a coinage word which is created by myself. I originally hoped it sounds like Dodge, but apparently many people called it Dockage, it is also acceptable.
The naming idea came from Twitch emotes like sadge, bedge or wokege. They all end in -ge.
The main objective of Dockge is to try to use the docker compose.yaml for everything. If you want to manage a single container, you can just use Portainer or Docker CLI.
Yes, you can. However, you need to move your compose file into the stacks directory:
- Stop your stack
- Move your compose file into
/opt/stacks/<stackName>/compose.yaml - In Dockge, click the " Scan Stacks Folder" button in the top-right corner's dropdown menu
- Now you should see your stack in the list
Yes or no. Portainer provides a lot of Docker features. While Dockge is currently only focusing on docker-compose with a better user interface and better user experience.
If you want to manage your container with docker-compose only, the answer may be yes.
If you still need to manage something like docker networks, single containers, the answer may be no.
Yes, you can.
Dockge is built on top of Compose V2. compose.yaml also known as docker-compose.yml.




