![Dozzle]()
Dozzle
Container
Realtime log viewer for docker containers.
Image details
Source details
Configuration
TypeContaineramir20/dozzle:latest--no-analyticsYes8080/tcp/var/run/docker.sock : /var/run/docker.socktraefik.enable=truetraefik.http.services.dozzle.loadbalancer.server.port=8080traefik.http.routers.dozzle.entrypoints=websecuretraefik.http.routers.dozzle.tls.certresolver=mydnschallengeTemplate by mediadepot
Standalone Install
Select an install method, to see config/commands for deploying Dozzle
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select Dozzle, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation, or see amir20/dozzle for app-specific guidance.
Dozzle - dozzle.dev
Dozzle is a small lightweight application with a web based interface to monitor Docker logs. It doesn’t store any log files. It is for live monitoring of your container logs only.
Features
- Intelligent fuzzy search for container names 🤖
- Search logs using regex 🔦
- Small memory footprint 🏎
- Split screen for viewing multiple logs
- Download logs easily
- Live stats with memory and CPU usage
- Multi-user authentication with support for proxy forward authorization 🚨
Dozzle has been tested with hundreds of containers. However, it doesn't support offline searching. Products like Loggly, Papertrail or Kibana are more suited for full search capabilities.
Getting Started
Dozzle is a small container (4 MB compressed). Pull the latest release with:$ docker pull amir20/dozzle:latestRunning Dozzle
The simplest way to use dozzle is to run the docker container. Also, mount the Docker Unix socket with--volume to /var/run/docker.sock:$ docker run --name dozzle -d --volume=/var/run/docker.sock:/var/run/docker.sock:ro -p 8888:8080 amir20/dozzle:latestHere is the Docker Compose file:
version: "3"
services:
dozzle:
container_name: dozzle
image: amir20/dozzle:latest
volumes:
- /var/run/docker.sock:/var/run/docker.sock:ro
ports:
- 8888:8080Technical Details
Dozzle users automatic API negotiation which works with most Docker configurations. Dozzle also works with Colima and Podman.Installation on podman
By default Podman doesn't have a background process but you can enable this for Dozzle to work.Verify first if your podman installation has enabled remote socket:
podman infoWhen you get under the key remote socket output like this, its already enabled:
remoteSocket:
exists: true
path: /run/user/1000/podman/podman.sockIf it's not enabled please follow this tutorial to enable it.
Once you have the podman remote socket you can run Dozzle on podman.
podman run --volume=/run/user/1000/podman/podman.sock:/var/run/docker.sock:ro -d -p 8888:8080 amir20/dozzle:latestSecurity
Dozzle supports file based authentication and forward proxy like Authelia. These are documented at https://dozzle.dev/guide/authentication.Analytics collected
Dozzle collects anonymous user configurations using Google Analytics. Why? Dozzle is an open source project with no funding. As a result, there is no time to do user studies of Dozzle. Analytics is collected to prioritize features and fixes based on how people use Dozzle. This data is completely public and can be viewed live using Data Studio dashboard.If you do not want to be tracked at all, see the
--no-analytics flag below.Environment variables and configuration
Dozzle follows the 12-factor model. Configurations can use the CLI flags or environment variables. The table below outlines all supported options and their respective env vars.| Flag | Env Variable | Default |
|---|---|---|
--addr | DOZZLEADDR | :8080 |
--base | DOZZLEBASE | / |
--hostname | DOZZLEHOSTNAME | "" |
--level | DOZZLELEVEL | info |
--auth-provider | DOZZLEAUTHPROVIDER | none |
--auth-header-user | DOZZLEAUTHHEADERUSER | Remote-User |
--auth-header-email | DOZZLEAUTHHEADEREMAIL | Remote-Email |
--auth-header-name | DOZZLEAUTHHEADERNAME | Remote-Name |
--enable-actions | DOZZLEENABLEACTIONS | false |
--wait-for-docker-seconds | DOZZLEWAITFORDOCKERSECONDS | 0 |
--filter | DOZZLEFILTER | "" |
--no-analytics | DOZZLENOANALYTICS | false |
--remote-host | DOZZLEREMOTEHOST |
Support
There are many ways you can support Dozzle:- Use it! Write about it! Star it! If you love Dozzle, drop me a line and tell me what you love.
- Blog about Dozzle to spread the word. If you are good at writing send PRs to improve the documentation at dozzle.dev
- Sponsor my work at https://www.buymeacoffee.com/amirraminfar
License
MITBuilding
To Build and test locally:Serve Dozzle on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying dozzle.example.com to http://dozzle:8080
Add this to your Caddyfile
dozzle.example.com {
reverse_proxy http://dozzle:8080
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs dozzle - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Published on a random port
This template exposes 8080/tcp without setting a host port,
so Docker picks a random free one on every deploy.
- Find it in the Ports column of Portainer's container list, or with
docker port dozzle
Can't reach the Docker socket
dozzle talks to Docker through /var/run/docker.sock. If the logs show
"permission denied while trying to connect to the Docker daemon socket", the app's user can't access it.
- Check the socket exists on the host:
ls -l /var/run/docker.sock - Run the container as root, or add the docker group's id to the container with
group_add.
Image won't pull
Test the pull directly on the host: docker pull amir20/dozzle:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64, arm64, arm/v7, arm/v6 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Privileged mode
This template runs the container in privileged mode, giving it full access to your host.
- Only deploy it if you trust the app.
- If deployment is blocked, your Portainer security settings or hardened host may not allow privileged containers.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on amir20/dozzle
- Template not working: Open an issue on mediadepot/templates
- This website not working: Open an issue on lissy93/portainer-templates
A single container
Dozzle runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything Dozzle needs bundled into one download. This template pulls amir20/dozzle:latest, which Docker fetches once (about 24 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. Dozzle's comes from Docker Hub, published by amir20.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is v10.7-alpine. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, arm/v6, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:
8080, published on a random host port
Volumes
A volume is where Dozzle keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/var/run/docker.sockfrom/var/run/docker.sockon the host, read-only (a socket it talks to, not storage)
Networking
Nothing custom is set, so Dozzle sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container dozzle. That's what you'll spot in the containers list and use in commands like docker logs dozzle.
Labels
Labels are small notes pinned to the container. They don't change how Dozzle behaves, but other tools read them, most often a reverse proxy like Traefik working out which apps to route where. This template sets:
traefik.enable=truetraefik.http.services.dozzle.loadbalancer.server.port=8080traefik.http.routers.dozzle.entrypoints=websecuretraefik.http.routers.dozzle.tls.certresolver=mydnschallenge
Startup command
The command is what runs the moment the container starts. This template sets its own, --no-analytics, in place of the image's default.
Privileged mode
This template runs Dozzle in privileged mode, which gives it nearly as much access to your server as the system itself. Some apps genuinely need it to reach hardware or manage the host, so it's one to run only if you trust the source.
Open source license
Dozzle is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Dozzle up. Add the template list to Portainer once, then deploying Dozzle is a click rather than a wall of config.