Skip to content

Docker integration

mish talks to the Docker Engine API read-only — only GET requests, never a mutation.

SourceData
/containers/json?size=1container list, SizeRw, SizeRootFs, image, state, labels
/containers/{id}/jsonmounts (type, source, destination, RW)
/containers/{id}/stats?stream=falseCPU %, memory used/limit, net RX/TX, block I/O
/images/json, /volumesimage and volume sizes

Do not mount docker.sock into the app. The shipped compose files run the GET-only tecnativa/docker-socket-proxy and point the core at it:

environment:
DOCKER_HOST: tcp://docker-socket-proxy:2375

The proxy sets POST=0 (GET/HEAD only) and EVENTS=0. Mounting the socket :ro is not a write barrier: the socket inode is read-only, but a connected client can still issue API requests. The proxy is the control.

Set MISH_DOCKER=false to disable Docker collection entirely; the core will not contact the endpoint and the Docker API routes return 404.

The collector accepts unix://, tcp:// and http:// endpoints.

No socket, permission denied, or rootless Docker/Podman → the Docker views report unavailable and everything else keeps working. Docker is never required.