Hi,
since several days, my HA installation became really slow, almost useless. UI crashes every other minute, Alexa and Apple Home have problem in sending command to UI.
I’m running HASS OS on a x64 minipc, I have HA from 5 year, and more than 1 year on this HW.
I did some investigation, and I think the reason of this lack of performance is related to the containers behind HA. I have a lot of identical logs in the Host registry
Dec 22 20:20:56 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-fc8db1ba81fa8e4fc1efe6e962c6a1b1c22db3153fe3fcdba2f0a23f467ffdcd-runc.ve78Ok.mount: Deactivated successfully.
Dec 22 20:20:58 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-b4f04e67d1a73ad21ea784e13b561666fda2150913c93d8915863e6e2274da4c-runc.EEzPUc.mount: Deactivated successfully.
Dec 22 20:20:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-8546a3eb45afbfe7ba92e255af53b8e35c932e77c44a2ac9aff1b32dbf0e6b97-runc.3vgVgt.mount: Deactivated successfully.
Dec 22 20:21:26 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-fc8db1ba81fa8e4fc1efe6e962c6a1b1c22db3153fe3fcdba2f0a23f467ffdcd-runc.9QmutO.mount: Deactivated successfully.
Dec 22 20:21:28 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-b4f04e67d1a73ad21ea784e13b561666fda2150913c93d8915863e6e2274da4c-runc.jzUyNk.mount: Deactivated successfully.
Dec 22 20:21:29 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-8546a3eb45afbfe7ba92e255af53b8e35c932e77c44a2ac9aff1b32dbf0e6b97-runc.F4kLGS.mount: Deactivated successfully.
Dec 22 20:21:56 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-fc8db1ba81fa8e4fc1efe6e962c6a1b1c22db3153fe3fcdba2f0a23f467ffdcd-runc.pZjFzJ.mount: Deactivated successfully.
Dec 22 20:22:56 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-fc8db1ba81fa8e4fc1efe6e962c6a1b1c22db3153fe3fcdba2f0a23f467ffdcd-runc.GekjlS.mount: Deactivated successfully.
Dec 22 20:22:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-b4f04e67d1a73ad21ea784e13b561666fda2150913c93d8915863e6e2274da4c-runc.75gZY6.mount: Deactivated successfully.
Dec 22 20:23:26 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-fc8db1ba81fa8e4fc1efe6e962c6a1b1c22db3153fe3fcdba2f0a23f467ffdcd-runc.FdJirn.mount: Deactivated successfully.
Dec 22 20:23:30 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-8546a3eb45afbfe7ba92e255af53b8e35c932e77c44a2ac9aff1b32dbf0e6b97-runc.sLDQHZ.mount: Deactivated successfully.
Dec 22 20:23:59 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-b4f04e67d1a73ad21ea784e13b561666fda2150913c93d8915863e6e2274da4c-runc.62TxE4.mount: Deactivated successfully.
Dec 22 20:24:30 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-8546a3eb45afbfe7ba92e255af53b8e35c932e77c44a2ac9aff1b32dbf0e6b97-runc.idiXKt.mount: Deactivated successfully.
These logs, thanks to another post in the community, led me to believe that some (or all) containers are constantly failing and being reactivated by the Watchdog.
I managed to understand which are the docker that keep getting deactivate:
b4f04e homeassistant/amd64-addon-configurator:5.7.0
8546a3 ghcr.io/hassio-addons/node-red/amd64:16.0.2
fc8db1 ghcr.io/hassio-addons/adguard/amd64:5.0.1
at this moment these are the only ones that are getting deactivated and activate all over again, but during the last 24 hours I noticed also others having the same behavior. How can I investigate more this issue? Where I can find the root cause of this activation/deactivation?
There must be something, maybe on docker side, that can points me in the right direction.
Thanks
Matteo