Closed drinfernoo closed 1 month ago
I've actually updated my YAML to not request these statistics:
monitor_docker:
- name: DockerPi
url: http://192.168.1.220:2375
monitored_conditions:
- state
- status
- uptime
- image
- 1cpu_percentage
containers:
- wyzesense2mqtt
rename:
wyzesense2mqtt: WyzeSense2MQTT
And I'm still getting the error from my previous comment... Which makes me feel like the integration isn't respecting my new YAML?
Actually, I only today noticed that there's a FAQ about getting memory stats from some platforms. After making that change on my (Raspbian) system, I no longer get the errors in my logs... but I'm still not configured to fetch the memory stats anyways, and am not getting the entities (as expected).
So, it still appears the integration is attempting to fetch memory stats even when not configured to do so.
On a semi-related note, what type of changes would need to be made to make this work for a Docker container running inside of an LXC container?
Is v1.11 an improvement with the TCP behavior?
Docker inside LXC should work, as long the TCP port is exposed (reachable).
I have the same issue. I have removed memory monitoring but I get single error when home assistant starts.
2022-08-15 21:00:37.728 ERROR (Thread-3 (RunDocker)) [custom_components.monitor_docker.helpers] [Docker2] dockerproxy: Cannot determine memory usage for container ('stats')
2022-08-15 21:00:37.817 ERROR (Thread-3 (RunDocker)) [custom_components.monitor_docker.helpers] [Docker2] dockerproxy: Raw 'memory_stats' {}
@drinfernoo what change did you make on raspberry pi?
This solved my issue: https://github.com/ualex73/monitor_docker/issues/26#issuecomment-723016034
I have a remote Docker instance being monitored with this component, and I keep seeing these errors in my logs:
My YAML looks like:
Also, the sensor entities (in my case,
sensor.dockerpi_memory
,sensor.dockerpi_memory_percent
,sensor.dockerpi_wyzesense2mqtt_memory
, andsensor.dockerpi_wyzesense2mqtt_memory_percent
) gets created, but with an unknown state.