Good morning community,
Something weird happening!
My config:
Home Assistant 2022.11.2
Supervisor 2022.10.2
Operating System 9.3
Frontend 20221108.0 - latest
Running on: Hyper-V Windows 10 (no judging! lol)
Adguard Addon installed and working, however, I have disable it, restarted about 10 times, and the messages are still showing!?
First, the logs below… I have about 120 lines of the same within the HOST Logs!
Am I going to live doctor? I just wanted to check if somebody that knows more about this can give me peace of mind that my system is not about to go bananas!
Not sure how to check from the console as it seems more like a runtime than a container! I know… I have no clue what I’m talking about… but I tried… read here and there…did some docker ps, etc… nothing. Gave up after 3 days of trying to figure it out myself!
Oh, I also downloaded a new image, restored from backup, nothing!
Nov 09 15:41:14 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.d8txzn.mount: Deactivated successfully.
Nov 09 15:41:44 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.6lJwa1.mount: Deactivated successfully.
Nov 09 15:42:14 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.Sfr7gx.mount: Deactivated successfully.
Nov 09 15:42:44 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.aZTRLV.mount: Deactivated successfully.
Nov 09 15:43:14 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.cPJJzb.mount: Deactivated successfully.
Nov 09 15:43:44 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.BIuDJm.mount: Deactivated successfully.
Nov 09 15:44:14 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.oP6gPW.mount: Deactivated successfully.
Nov 09 15:44:44 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.y6tpmg.mount: Deactivated successfully.
Nov 09 15:45:14 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.AVPJzc.mount: Deactivated successfully.
Nov 09 15:45:45 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.GOfKMd.mount: Deactivated successfully.
Nov 09 15:46:15 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.vvJkMy.mount: Deactivated successfully.
Nov 09 15:46:45 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-a37b3af4ea930124769ac478f76b4af622af1fac3f91123077635099903b2135-runc.3BtIJy.mount: Deactivated successfully.
I am getting the same thing, no idea what it’s about. I was checking logs because i am getting HA locking up or becoming disconnected every 12-24 hours or so. Having to reboot every day to be able to connect.
Based on the post of @Bellavista (which works like a charm if you use the right SSH add-on : “Advanced SSH & Web Terminal” without protection mode!), this is my conclusion:
Every add-on that has the watchdog enabled, will generate mounting logs in the Host logs file.
I assume that this is the way the watch dog works… trying to mount again and again.
For me it was Node red, and the Configurator add-on.
Hi,
I’m having the same issue in my installation (HA OS on miniPC).
Thanks to this topic I managed to understand that the Watchdogs is mounting all over again several container, and I think this leads to the slowness and unresponsiveness (is it a word?) of my installation.
But I think the issue is not the mounting it self, that is just a consequence (which has as a consequence the slowness of HA). Since a lot of container are failing and being mounted again, there must be a common cause somewhere else.
But how can I investigate this?
There are other logs that can help?
Old-ish thread, but for anyone worrying about this and ending up here, this is completely normal (even though it is admittedly very annoying). These log entries are related to docker’s health checks. See here.
My system (HAOS 12. on Rasberry pi4, Supervisor 2024.03) has the same behavior: Constant “run-docker-runtime\x2drunc-moby… mount Deactivated”
Following vroom’s comment. If you follow the link he/she posted. The log entries are docker healthcheck logs. I was personnally worried the log would fill my disk since it grows by about 100MB per day. But after investigation the journaling is limited to 500MB. I found this configuration in ./etc/systemd/journald.conf.
The entry is:
[Journal]
Storage=auto
Compress=yes
SystemMaxUse=500M
So this might be annoying if you ever need to search for something in the logs but it all seems OK.
Still, I can’t understand why this needs to be logged so consistently.
Anyway my worries of disk overflow are put to rest… for now.
: “Advanced SSH & Web Terminal” without protection mode!), this is my conclusion: