Does Dozzle store my logs?

No. Dozzle is completely stateless. It reads the Docker log stream live and forwards it to your browser — nothing is written to disk. If you need log retention and search, pair Dozzle with a dedicated log aggregator such as Loki.

Is it safe to give Dozzle access to the Docker socket?

Dozzle mounts the Docker socket read-only (`/var/run/docker.sock:ro`). It can only read logs and list containers — it cannot start, stop, restart or modify any container or image. Grant access only to users you trust, and restrict port 8080 to authorised IPs or put it behind auth.

How much RAM does Dozzle use?

Under 10 MB at idle. The Go binary is minimal: it keeps no in-memory log buffer and streams data directly from Docker to the WebSocket connection. It is safe to co-locate Dozzle on any VPS alongside your main application.

Can Dozzle monitor containers on multiple servers?

Yes. Run the `dozzle agent` mode on each remote Docker host (port 7007) and point your main Dozzle instance at them via the `DOZZLE_REMOTE_AGENT` environment variable. All remote containers appear in the same unified UI.

What is the difference between Dozzle and Beszel?

Dozzle shows container logs (text output) in real time. Beszel tracks resource metrics (CPU, RAM, disk, network) and charts them over time. They complement each other perfectly: use Dozzle when you need to read what a container is printing, and Beszel when you need to know how much CPU or RAM it is consuming.

Superviser les infrastructures.

Dozzle

Real-time Docker log viewer — stream, search and tail all your container logs from the browser, stateless, under 10 MB RAM.

~10 Mo RAM 1 vCPU Port 8080 Disponible

Code source

Stack technique

DockerGo

RAM minimum~10 Mo

CPU minimum1 vCPU

Port par défaut8080

OS compatiblesubuntu-24.04

Dozzle is a real-time log viewer for Docker containers. It connects to the Docker socket (read-only) and streams logs from every container running on your host directly into the browser — no log storage, no database, no persistent state. The Go binary uses under 10 MB RAM at idle and starts in under a second.

Made by Amir Raminfar (MIT, ~12 k GitHub stars), Dozzle gives you live tail, full-text search across all containers, split-view multi-container comparison, and an optional agent mode for monitoring containers on remote Docker hosts. It is the fastest way to move from `docker logs -f` chaos to an organised, browser-based log console on any VPS.

Fonctionnalités clés

Live log streaming from all Docker containers — no polling delay, WebSocket-based real-time tail.

Full-text search across container logs — filter by keyword or regex without leaving the browser.

Multi-container split view — pin several containers side-by-side to correlate log events.

Remote agent mode — one Dozzle hub aggregates logs from containers on multiple Docker hosts.

Read-only Docker socket access — Dozzle cannot start, stop or modify your containers.

Stateless by design — no database, no log retention, no disk writes; restarts in under a second.

Under 10 MB RAM — negligible overhead; safe to co-locate on any running VPS.

MIT license — no paywalled features, no cloud account required.

Quand utiliser cette solution ?

1

Live debugging during deploy

After pushing a new release, open Dozzle and tail the app container in real time. Errors surface in the browser immediately — no need to SSH and run `docker logs` from the command line.

2

Multi-container correlation

Split-view two containers — your API and your database — side-by-side to match a slow query log line with the exact API request that triggered it.

3

Lightweight log console for a shared team

Give developers read-only visibility into production logs without granting them SSH access. Dozzle's optional basic-auth or OIDC login gates access without complex tooling.

Déployer Dozzle sur votre VPS

Guide optimisé pour les VPS Cloud ServOrbit.

01

Create the VPS

Order a 1-vCPU / 512 MB RAM VPS on ServOrbit. Ubuntu 22.04 is recommended. Dozzle is so lightweight that it runs alongside any existing workload without measurable impact.

02

Deploy Dozzle

Connect via SSH and run: docker run -d --restart=always -p 8080:8080 -v /var/run/docker.sock:/var/run/docker.sock:ro --name dozzle amir20/dozzle:latest. Dozzle is immediately accessible on port 8080 — no initial setup, no account creation required.

03

Open the log console

Navigate to http://:8080 in your browser. Dozzle lists every running container on the left. Click any container to start tailing its logs. Use the search bar at the top to filter by keyword or regex in real time.

04

Optional: restrict access

Dozzle exposes all container logs to anyone who can reach port 8080. In production, place it behind a reverse proxy with authentication: set DOZZLE_USERNAME and DOZZLE_PASSWORD environment variables to enable built-in basic auth, or configure OIDC in dozzle.yml. Restrict the port with ufw allow from to any port 8080 if you only need personal access.

05

Optional: multi-host with agents

To monitor Docker containers on other servers, run amir20/dozzle:latest agent on each remote host (exposes port 7007). In the main Dozzle instance, set DOZZLE_REMOTE_AGENT to the list of agent endpoints and all remote containers appear in the same UI.

Questions fréquentes

Dozzle is a real-time, browser-based log viewer for Docker containers. It streams logs from every container on your host directly to the browser via WebSocket — no database, no log storage, no persistent state.

Solutions complémentaires

Monitoring & Observabilité

Activez Dozzle sur votre infrastructure.

VPS Cloud dédié — IPv4 incluse, datacenter européen, support inclus. Vos données ne quittent jamais votre serveur.

Configuration recommandée : ~10 Mo RAM · 1 vCPU