Filtering Containers
Dozzle supports conditional filtering similar to Docker's --filter with DOZZLE_FILTER
or --filter
. Filters are passed directly to Docker to limit what Dozzle can see. For example, filtering by label is supported with --filter "label=color"
, which is similar to docker ps
command with docker ps --filter "label=color"
.
docker run --volume=/var/run/docker.sock:/var/run/docker.sock -p 8080:8080 amir20/dozzle --filter label=color
services:
dozzle:
image: amir20/dozzle:latest
volumes:
- /var/run/docker.sock:/var/run/docker.sock
ports:
- 8080:8080
environment:
DOZZLE_FILTER: label=color
Common filters are name
or label
to limit Dozzle's access to containers.
UI, Agents, and User Filters New
Dozzle supports multiple filters to limit the containers it can see. Filters can be set at the UI, agent, or user level.
- UI Filters: These filters are applied to the Dozzle UI instance and sent to Docker to restrict the visible containers. They affect all agents and users who do not have their own filters.
- Agent Filters: These filters are set at the agent level and sent to Docker to limit the containers exposed by that agent. Agent filters and UI filters work together to restrict the containers.
- User Filters: These filters are set at the user level and determine which containers the user can see. If user filters are not defined, Dozzle defaults to using the UI filters.
For more information on setting filters for specific users, see user filters. For details on setting filters for agents, see agent filters.
WARNING
It is important to understand that multiple filters are combined to limit the containers. For example, if you set --filter label=color
at the UI level and --filter label=type
at the agent level, Dozzle will only display containers that have both the color
and type
labels.