Deploy DUMB¶
Choose the host or management tool where you want to install DUMB. Each link below opens the complete installation guide for that platform.
After installation, you will use the DUMB dashboard for everyday setup, service controls, updates and logs. The deployment guide covers the host setup needed to reach that dashboard.
| Your environment | Guide | What it manages |
|---|---|---|
| Linux terminal | Docker Compose | Compose file, storage, and container lifecycle |
| Existing Portainer installation | Portainer | DUMB as a Portainer stack |
| Existing Dockge installation | Dockge | DUMB as a Compose stack |
| Unraid | Unraid | Community Applications template and host paths |
| Windows | WSL2 | Docker Engine in a Linux distribution |
| Proxmox | Native LXC | DUMB and managed services directly in a Debian guest |
| Synology | Container Manager | A Compose project with NAS storage |
| QNAP | Container Station | A Compose application with shared folders |
| TrueNAS SCALE | Custom App | A Compose-based app with datasets |
The native Proxmox helper has its own validation status and runtime requirements; read its guide before treating it as equivalent to the Docker image.
Choose an installation path¶
Start with the host you already use. The platform links below provide the exact storage and installation steps.
flowchart TD
Host["Where will DUMB run?"] --> Linux["Linux or a Docker host"]
Host --> Windows["Windows: prepare WSL2 first"]
Host --> NAS["NAS: use its Compose editor"]
Host --> Proxmox["Proxmox: review native LXC validation"]
Linux --> Terminal["Terminal: Docker Compose"]
Linux --> Web["Web management: Portainer or Dockge"]
Windows --> Linux
NAS --> Editors["Synology, QNAP, TrueNAS or Unraid guide"]
Terminal --> Dashboard["Open DUMB and complete onboarding"]
Web --> Dashboard
Editors --> Dashboard
Proxmox --> Dashboard
Before starting¶
Read Before you install for credentials, sizing, permissions, and persistence. Every normal deployment preserves these paths:
| Path | Purpose |
|---|---|
/config |
DUMB configuration and feature state |
/log |
DUMB and service logs |
/data |
Application data mapped through DUMB-managed internal paths |
/mnt/debrid |
Mounts and library paths |
DUMB creates dumb_config.json when needed. Keep the host directories when replacing the container.
Choose the network and mount layout¶
The default Compose file publishes port 3005 for the dashboard, REST gateway, and WebSockets. Embedded service UIs can use that same address. Publish individual service ports only when clients need direct access. See Networking and ports.
Use a normal /mnt/debrid bind if all consumers run inside DUMB. External consumers of FUSE/rclone submounts need a prepared shared Linux host mount and suitable propagation. See Before you install.
Windows hosts
Docker Desktop cannot provide the bind propagation required for external FUSE consumers. Use the WSL2 guide for Docker Engine on Windows.
After starting¶
- Open
http://<host>:3005. - Configure access and select services in Onboarding.
- Check service logs and finish application-specific setup.
- Test an import and playback through the applications you selected.
Keep a backup before changing persistent storage or moving hosts.
Development update · not in the released 2.23.0 docs
The development backend provides installation backup and restore.