Hass.io - Exposing docker.sock for docker_monitor

Installation Home Assistant OS
1

I noticed this morning that the ha-dockermon sensor has been depreciated in favour of docker_monitor however unlike dockermon which relies on a docker container of its own, docker_monitor requires docker.sock to be exposed to the homeassistant container.

If I was using the homeassistant docker container without Hass.io, i’d mount the file using the “-v /var/run/docker.sock:/var/run/docker.sock” flag and away we go - however from what i can see the supervisor controls the homeassistant container, so is this possible using Hass.io?

2

It is monitor so read only mount is likely best and will be OK.

-v /var/run/docker.sock:/var/run/docker.sock:ro

EDIT
Look like NO, docker-monitor need mount when build container.
BUT why not continue use ha-dockermon? It should continue to function since it is using HA Rest Integration for connection with HA

3

It’s depreciated in favour of the new custom component linked in first post. It’s not that clear from the docs if you need that mount… (to me anyway)

4

Seems to also replace Phil Hawthorne’s docker hadockermon???

Would be nice to see how to use this with hass.io and a configuration example for that as well as HACS. Until then I’m not changing either.

5

Based on my reading of how the sensor works, yeah it effectively means that the docker container is redundant.

It also does not appear to have the ability to monitor ‘remote’ docker instances either like hadockermon can - I’m currently monitoring an instance on a RPi and my Synology box as well as the one on my HA Server

6

I just fall in to same situation :slight_smile:
This looks helpful: https://cyberjunky.nl/docker-monitor-sensor-for-home-assistant/