Ich habe ioBroker (buanet/iobroker:v5.1.0) auf einem Raspberry Pi laufen und dieser verursacht jede Menge Einträge in /var/log/syslog:
Code
Jan 27 08:31:18 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-8c15a9f3ad9a9d22af19749459a3668f142b8dbb5804403470e90a904e900919-runc.VVkZDJ.mount: Succeeded.
Jan 27 08:31:18 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-8c15a9f3ad9a9d22af19749459a3668f142b8dbb5804403470e90a904e900919-runc.VVkZDJ.mount: Succeeded.
Jan 27 08:31:34 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.PUhlDh.mount: Succeeded.
Jan 27 08:31:34 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.PUhlDh.mount: Succeeded.
Jan 27 08:31:44 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.oHCzhh.mount: Succeeded.
Jan 27 08:31:44 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.oHCzhh.mount: Succeeded.
Jan 27 08:31:54 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.MrjX6t.mount: Succeeded.
Jan 27 08:31:54 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.MrjX6t.mount: Succeeded.
Jan 27 08:32:14 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.hJeJMN.mount: Succeeded.
Jan 27 08:32:14 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.hJeJMN.mount: Succeeded.
Jan 27 08:32:34 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-8c15a9f3ad9a9d22af19749459a3668f142b8dbb5804403470e90a904e900919-runc.Ol6Hqt.mount: Succeeded.
Jan 27 08:32:34 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-8c15a9f3ad9a9d22af19749459a3668f142b8dbb5804403470e90a904e900919-runc.Ol6Hqt.mount: Succeeded.
Jan 27 08:32:34 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.4SNfF4.mount: Succeeded.
Jan 27 08:32:34 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.4SNfF4.mount: Succeeded.
Jan 27 08:32:49 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-8c15a9f3ad9a9d22af19749459a3668f142b8dbb5804403470e90a904e900919-runc.wslnMI.mount: Succeeded.
Jan 27 08:32:49 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-8c15a9f3ad9a9d22af19749459a3668f142b8dbb5804403470e90a904e900919-runc.wslnMI.mount: Succeeded.
Jan 27 08:33:04 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-8c15a9f3ad9a9d22af19749459a3668f142b8dbb5804403470e90a904e900919-runc.e6AN5Q.mount: Succeeded.
Jan 27 08:33:35 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.dUJX0W.mount: Succeeded.
Jan 27 08:33:35 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.dUJX0W.mount: Succeeded.
Jan 27 08:34:16 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.6WHiRp.mount: Succeeded.
Jan 27 08:34:16 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.6WHiRp.mount: Succeeded.
Jan 27 08:34:35 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-8c15a9f3ad9a9d22af19749459a3668f142b8dbb5804403470e90a904e900919-runc.NuVKOM.mount: Succeeded.
Jan 27 08:34:35 pimaster systemd[1]: run-docker-runtime\x2drunc-moby-8c15a9f3ad9a9d22af19749459a3668f142b8dbb5804403470e90a904e900919-runc.NuVKOM.mount: Succeeded.
Jan 27 08:34:36 pimaster systemd[5441]: run-docker-runtime\x2drunc-moby-727671ab95147e728a713fa074a748631a7c9a585cab1be84ae6f04a06692639-runc.zBWnzH.mount: Succeeded.
Alles anzeigen
Ich habe schon danach gegoogelt und gesehen das wohl der Health Check des Containers dafür verantwortlich sein könnte.
Ich weiß nur nicht ob der Container jetzt wirklich andauernd irgendwas mountet oder nur Logfiles schreibt. Beides ist nicht so gut für die SSD.
Hat jemand eine Idee wie man entweder oder und den Healthcheck abstellt und die Ausgabe von systemd zum Schweigen bringt?