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.

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.

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.

Monitor your infrastructure.

Dozzle

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

~10 MB RAM 1 vCPU Port 8080 Available

Source code

Tech stack

DockerGo

Minimum RAM~10 MB

Minimum CPU1 vCPU

Default port8080

Compatible OSubuntu-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.

Key features

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.

When to use this 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.

Deploy Dozzle on your VPS

Guide optimized for ServOrbit Cloud VPS.

01

Order a ServOrbit VPS

Dozzle reads the logs of the containers running on the machine it sits on: install it on the VPS whose applications you want to follow. Its footprint is so small that it lives alongside an existing workload without any measurable impact — a 512 MB RAM plan is plenty.

02

Deploy Dozzle from the Marketplace

In your ServOrbit client area: Marketplace → Monitoring → Dozzle → Deploy. The stack starts the amir20/dozzle:latest image, mounts /var/run/docker.sock read-only and publishes the interface on 127.0.0.1:8080. There is no initial setup and no account to create: Dozzle is ready as soon as the container starts.

03

Open it for the first time

Careful, this is a security point and not a detail: Dozzle opens straight onto your containers' logs, with no credentials at all. Anyone who reaches its address reads everything your applications print — error messages, requests, sometimes tokens. That is exactly why ServOrbit attaches no domain to it: access goes through an SSH tunnel, ssh -L 8080:127.0.0.1:8080 root@<your-vps-ip>, then http://localhost:8080. 8080 is the catalogue port; use the one shown on your application card in the client area.

04

Open the log console

At the far end of the tunnel, the console answers on http://localhost:8080. Dozzle lists every running container in the left-hand column: click one to follow its output live. The search bar at the top filters by keyword or regular expression, in real time.

05

Protect access

Dozzle exposes every log line to anyone who reaches its address, which is why this installation stays bound to the loopback interface, with no public address. Authentication does exist upstream — a users.yml file generated by docker run amir20/dozzle generate declares the accounts, and DOZZLE_AUTH_PROVIDER also accepts an OIDC provider — but the catalogue recipe sets none, and we will not publish the app behind a domain until it does: application logs are the most talkative thing a server holds.

06

Read logs from several hosts

To follow containers on other servers too, run amir20/dozzle:latest agent on each remote host — it listens on port 7007 — then list those agents in the DOZZLE_REMOTE_AGENT variable of the main instance. All the remote containers then show up in the same interface, alongside those of the local machine.

Frequently asked questions

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.

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.

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.

Embed the deploy button

Maintaining a project that uses Dozzle? This button lets your readers deploy it on a VPS in one click, without reading Docker documentation.

Markdown

[![Deploy Dozzle on ServOrbit](https://servorbit.com/brand/deploy/button.svg)](https://servorbit.com/vps-cloud?template=dozzle&utm_source=deploy-badge&utm_medium=referral&utm_campaign=dozzle)

HTML

<a href="https://servorbit.com/vps-cloud?template=dozzle&utm_source=deploy-badge&utm_medium=referral&utm_campaign=dozzle"><img src="https://servorbit.com/brand/deploy/button.svg" alt="Deploy Dozzle on ServOrbit" height="40"></a>

The button points to a VPS order with the template preselected. The image is served from servorbit.com — nothing to host on your side.

Complementary solutions

Monitoring & Observability

Activate Dozzle on your infrastructure.

Dedicated Cloud VPS — IPv4 included, European datacenter, support included. Your data never leaves your server.

Recommended configuration: ~10 MB RAM · 1 vCPU