# Dockge

> Self-hosted Docker compose.yaml stack manager.

- Category: Home Lab & Self-Hosting
- Difficulty: beginner
- Components: dockge
- Tags: dockge, docker, compose, management
- Source: https://docker.recipes/homelab/dockge

## Overview

Dockge is a self-hosted Docker Compose stack manager developed by Louis Lam, the creator of Uptime Kuma. It provides a beautiful web interface for managing Docker Compose stacks without abstracting away the underlying YAML files. Unlike database-driven container management tools, Dockge works directly with real compose.yaml files stored on your filesystem, making it transparent and allowing direct file editing when needed. This approach ensures you're never locked into a proprietary format and can always fall back to standard Docker Compose commands. The application focuses on simplicity and visual appeal, offering an intuitive way to deploy, monitor, and manage multi-container applications through a clean web interface. Dockge is particularly valuable for homelab enthusiasts, system administrators, and developers who want the convenience of a GUI without sacrificing the flexibility and portability of standard Docker Compose files. The tool bridges the gap between command-line Docker Compose management and heavy-weight orchestration platforms, providing just enough abstraction to improve usability while maintaining full compatibility with the Docker Compose ecosystem.

## Features

- Visual Docker Compose stack management with real-time container status monitoring
- Direct file-based storage in /opt/stacks directory with no database dependencies
- Beautiful web interface inherited from Uptime Kuma's design philosophy
- In-browser YAML editor with syntax highlighting for compose files
- One-click stack deployment, updates, and teardown operations
- Real-time log viewing for individual containers within stacks
- Stack templates and import functionality for rapid deployment
- Mobile-responsive interface for managing stacks from any device

## Use cases

- Homelab managers organizing multiple self-hosted services into logical stacks
- Development teams needing visual oversight of local Docker Compose environments
- System administrators managing Docker applications across multiple servers
- DevOps engineers providing non-technical team members access to deployment controls
- Students learning Docker Compose with immediate visual feedback
- Small businesses running containerized applications without Kubernetes complexity
- Content creators and streamers managing media server stacks with quick controls

## Prerequisites

- Docker Engine installed and running on the host system
- Docker Compose plugin or standalone Docker Compose installation
- At least 512MB available RAM for the Dockge container
- Port 5001 available and accessible for the web interface
- Write permissions to /opt/stacks directory for stack file management
- Basic understanding of Docker Compose YAML syntax and container concepts

## docker-compose.yml

```yaml
services:
  dockge:
    image: louislam/dockge:latest
    container_name: dockge
    restart: unless-stopped
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - dockge_data:/app/data
      - /opt/stacks:/opt/stacks
    ports:
      - "5001:5001"

volumes:
  dockge_data:
```

## .env

```bash
# Stacks stored in /opt/stacks
```

## Usage notes

- Docs: https://github.com/louislam/dockge
- Access at http://localhost:5001
- Edit compose.yaml files directly in beautiful UI
- Stacks stored in /opt/stacks - real files, not database
- By Uptime Kuma creator - similar beautiful UI
- Perfect for managing homelab compose stacks visually

## Troubleshooting

- Permission denied accessing /var/run/docker.sock: Add user to docker group or run container with appropriate permissions
- Cannot create files in /opt/stacks: Ensure the directory exists and has proper write permissions for the container user
- Stacks fail to deploy with 'network not found' errors: Check that referenced networks exist or are defined in the compose file
- Interface shows 'connection refused' for containers: Verify container ports are properly exposed and not conflicting with host services
- Stack updates don't reflect changes: Clear browser cache and ensure file timestamps are newer than cached versions
- Memory errors during stack deployment: Increase Docker daemon memory limits or reduce concurrent stack operations

