This page documents the containerised application stack running on the
debian-dockervirtual machine. It includes directory layout, configuration standards, update practices, and tools used to manage and monitor services.
All Docker container stacks are organised under:/home/raven/dockerdata/
Each application has its own subdirectory containing:
docker-compose.yml.env fileconfig/ or data/ folders for persistent volumesExample Layout:dockerdata/
├── <service-name>/
│ ├── docker-compose.yml
│ ├── .env
│ └── config/ or data/
All containers are run as the raven user, with ownership set to UID/GID 1000:1000.
All services are deployed using Docker Compose.
Example base configuration:
services:
example-service:
image: example/image:latest
container_name: example-service
restart: unless-stopped
volumes:
- ./config:/config
- /mnt/wd-media:/mnt/wd-media:ro
environment:
- TZ=Australia/Queensland
networks:
- defaultOwnership and permissions:
sudo chown -R 1000:1000 /home/raven/dockerdata/*
To launch a service stack:
cd ~/dockerdata/<stack>
docker compose up -d
To update a single stack manually:
docker compose pull
docker compose up -d
Portainer is available for web-based container management: portainer.vibehub.one
Nginx Proxy Manager (NPM) handles reverse proxying and SSL certificates
Watchtower runs in the background and automatically updates most containers (excluding critical apps like Authentik or Home Assistant, which are updated manually)
To view logs:
cd ~/dockerdata/<stack>
docker compose logs -f
To clean up unused resources:
docker system prune -af --volumes
Common issues to check:
/mnt/wd-media)docker network ls)