dozzle-agent¶
dozzle-agent is the part of Dozzle that reads a host's container logs and serves them to a Dozzle server elsewhere. No host lists it, and no stack includes it. See Not in the plan.
Every VM already runs the same agent inside system-agent, so a host in the plan never needs this stack.
To run it on a host of your own, see Applications (ap01).
What it runs¶
| Service | Does |
|---|---|
dozzle-agent |
Serves the host's container logs to a Dozzle server, on port 7007 |
socket-proxy |
Gives the agent a filtered, read-only view of the Docker socket |
The project is dozzle, and the containers are dozzle-dozzle-agent and dozzle-socket-proxy.
The agent keeps nothing on disk.
Values it reads¶
This stack reads no Variable or Secret of its own.
It also reads the 19 operational defaults, as every stack does.
What the host needs¶
The project is dozzle, so the stack's folders sit under /opt/docker/volumes/dozzle and /opt/docker/logs/dozzle. Both are mode 0750, owned by the admin account with group 101000.
No container in this stack has a folder of its own.
| Port | Allowed from | Comment |
|---|---|---|
7007/tcp |
The internal subnet | Dozzle agent |
The host's NixOS configuration creates the folders and opens the ports when the host is deployed. It reads them from the host's file in the private repo, nixos/hosts/<host>.json, which nixos-sync.yml writes from the stack's setup.yaml. See Host layout.
The stack has no route, so it needs no Traefik on the host.
The agent in system-agent publishes port 7007 as well. A host runs one or the other.
Verify¶
On the host, list the Stack's containers. Komodo names the Compose project after the Stack, not after PROJECT_NAME:
Both containers show healthy in the STATUS column.
The agent has no interface of its own. Its logs appear in a Dozzle server that names the host as a remote agent. See dozzle-server.