Dozzle
Dozzle is a lightweight, real-time log viewer for Docker containers that runs entirely in the browser. It connects to Docker via the socket and streams container logs in real-time with syntax highlighting, regex search, and multi-container log merging. Dozzle requires no database and stores no data — it is a pure log viewer that reads logs directly from the Docker engine. It features automatic container discovery, fuzzy search across container names, log downloading, dark/light theme, and a responsive design that works on mobile. The Docker socket is mounted read-only for security, giving Dozzle read access to container metadata and logs without the ability to modify containers. After deployment, access the web UI on port 8080 to see all running containers and their logs in real-time.
Services Inclus
dozzle
amir20/dozzle:latest
Variables d'Environnement :
YAML Généré
# Generated by ComposeHub (composehub.dev)
name: dozzle
services:
dozzle:
image: amir20/dozzle:latest
restart: always
ports:
- 8080:8080
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
environment:
DOZZLE_LEVEL: ${DOZZLE_LEVEL:-info}
DOZZLE_TAILSIZE: ${DOZZLE_TAILSIZE:-300}
DOZZLE_NO_ANALYTICS: ${DOZZLE_NO_ANALYTICS:-true}
DOZZLE_AUTH_PROVIDER: ${DOZZLE_AUTH_PROVIDER:-none}
networks:
- dozzle
healthcheck:
test:
- CMD-SHELL
- wget --no-verbose --tries=1 --spider http://localhost:8080/healthcheck || exit 1
interval: 30s
timeout: 10s
retries: 3
start_period: 10s
deploy:
resources:
limits:
cpus: "0.50"
memory: 128M
reservations:
cpus: "0.05"
memory: 32M
labels:
com.composehub.description: Dozzle real-time Docker log viewer
networks:
dozzle:
driver: bridge
Informations Rapides
- Services
- 1
- Réseaux
- 1
- Volumes
- 0
Quand l'Utiliser
Ce modèle est idéal pour mettre en place un environnement dozzle Tous les services sont préconfigurés avec des healthchecks, des limites de ressources et des valeurs par défaut raisonnables. Personnalisez les variables d'environnement avant de déployer en production.
Conseils
- Changez tous les mots de passe par défaut avant le déploiement
- Vérifiez les limites de ressources pour votre matériel
- Ajoutez un reverse proxy pour le HTTPS en production
- Configurez des stratégies de sauvegarde pour les volumes de données