Skip to content

Dozzle vs docker logs ​

Dozzle reads the same logs as docker logs. Nothing is copied or stored, so it never shows anything the command could not. What it changes is how you read them: in a browser, across containers and hosts, without a shell on the server.

At a glance ​

Dozzledocker logs
Where you read themA browser, from any deviceA shell on the Docker host
Several containersAny set of containers in one merged view, or a whole stack or serviceOne container. docker compose logs covers a project
Several hostsOne UI for every host, through agentsOne host per shell, or a DOCKER_HOST per command
SearchingSearch as you type, with regular expressionsPipe to grep
JSON logsFormatted and color coded, SQL over fieldsRaw lines, pipe to jq
Stack tracesMulti-line entries grouped togetherOne line at a time
CPU and memoryCharts next to the logsdocker stats in another shell
SharingA link to a container, behind authenticationCopy and paste
InstallOne containerAlready there

When the terminal is enough ​

If you are already on the host and want the last hundred lines of one container, docker logs --tail 100 -f <name> is the quickest way. For a live view of every container in a terminal, dtop shows them in a docker ps-style table and opens Dozzle when you need the full logs.

When Dozzle fits better ​

Use Dozzle when more than one person reads the logs, when you would rather not hand out SSH access to read them, or when you are following one request through several containers at once. It is also the easier way to read logs from a phone.

Try it ​

sh
docker run -d -v /var/run/docker.sock:/var/run/docker.sock -v dozzle_data:/data -p 8080:8080 amir20/dozzle:latest

Then open http://localhost:8080. More options are in Getting Started.

Released under the MIT License. Open sourced and sponsored by Docker OSS.