Introduction

Dozzle is an open-source, self-hosted tool for viewing and monitoring the logs of Docker containers.

Here are the key points about Dozzle:

It gives you a web interface so you can see container logs in real time instead of having to use docker logs … on the command line.
It is lightweight, doesn’t store logs permanently (unless configured otherwise), and is designed for quick troubleshooting and debugging.
Made by Amir Raminfar, released under the MIT license.

Some of the useful capabilities of Dozzle include:

Real-time log streaming from containers.
Support for Docker, as well as Docker Swarm and Kubernetes.
Multi-host or remote-agent mode, so you can monitor containers across different machines.
A SQL engine (with WebAssembly and DuckDB) so you can run queries over logs in the browser.
Authentication support (file-based or via forward proxy) so you can restrict who can see logs.
Some safety/utility features like toggling shell access, container actions (start/stop/restart) but usually off by default for security.

You can install and run Dozzle using various setups:

Standalone Docker container, mounting the Docker socket so Dozzle can access container logs.
Docker Compose setups.
In Docker Swarm (global mode) to monitor across nodes.
Kubernetes mode.

Security: Because Dozzle need access to the Docker socket (or remote hosts), there are security implications. If compromised, that access could be risky.
Log storage: By default, Dozzle doesn’t persist logs on its own (it just shows what the container is outputting live). If you need long-term log storage, archival, or more advanced search history, you’ll need to combine it with other tools.
Features vs full logging stacks: For big, enterprise-scale logging, tools like ELK stack, Grafana Loki, etc., might offer more in terms of aggregation, indexing, alerting. Dozzle is optimized for simplicity and real-time visibility.