host log full of homeassistant systemd[1]: run-docker-runtime\xxxx .mount: Deactivated successfully.

[Bellavista]

I need help!
i have a host log full of
Jan 31 23:44:24 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-554a681a96db9c07c12e921af7ddf5c93065fbf535473d5c57b6fc7f64e48ae0-runc.rr5hbP.mount: Deactivated successfully.
Jan 31 23:44:55 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-554a681a96db9c07c12e921af7ddf5c93065fbf535473d5c57b6fc7f64e48ae0-runc.50PtzL.mount: Deactivated successfully.
Jan 31 23:45:25 homeassistant systemd[1]: run-docker-runtime\x2drunc-moby-554a681a96db9c07c12e921af7ddf5c93065fbf535473d5c57b6fc7f64e48ae0-runc.YOPLdi.mount: Deactivated successfully.
And the docker 554a681a96db is the adguard addon

can someone help me to undstand the problem
what i can do to undstand ....a suggestion on how to analyze the problem
Thank

[Bellavista]

i restarted Adguard in debug mode and this is the log

Home Assistant Core: 2023.1.4
Home Assistant Supervisor: 2023.01.1

Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.

s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
Log level is set to DEBUG
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-adguard: starting
[00:30:45] DEBUG: Requested API resource: http://supervisor/network/info
[00:30:45] DEBUG: Request method: GET
[00:30:45] DEBUG: Request data: {}
[00:30:45] DEBUG: API HTTP Response code: 200
[00:30:45] DEBUG: API Response: {"result": "ok", "data": {"interfaces": [{"interface": "enp0s3", "type": "ethernet", "enabled": true, "connected": true, "primary": true, "ipv4": {"method": "static", "address": ["192.168.1.10/24"], "nameservers": ["192.168.1.1"], "gateway": "192.168.1.1", "ready": true}, "ipv6": {"method": "disabled", "address": ["fe80::2552:74f5:92f8:d799/64"], "nameservers": [], "gateway": null, "ready": true}, "wifi": null, "vlan": null}], "docker": {"interface": "hassio", "address": "172.30.32.0/23", "gateway": "172.30.32.1", "dns": "172.30.32.3"}, "host_internet": true, "supervisor_internet": true}}
s6-rc: info: service init-nginx successfully started
[00:30:50] DEBUG: Requested API resource: http://supervisor/network/interface/enp0s3/info
[00:30:50] DEBUG: Request method: GET
[00:30:50] DEBUG: Request data: {}
[00:30:50] DEBUG: API HTTP Response code: 200
[00:30:50] DEBUG: API Response: {"result": "ok", "data": {"interface": "enp0s3", "type": "ethernet", "enabled": true, "connected": true, "primary": true, "ipv4": {"method": "static", "address": ["192.168.1.10/24"], "nameservers": ["192.168.1.1"], "gateway": "192.168.1.1", "ready": true}, "ipv6": {"method": "disabled", "address": ["fe80::2552:74f5:92f8:d799/64"], "nameservers": [], "gateway": null, "ready": true}, "wifi": null, "vlan": null}}
s6-rc: info: service init-adguard successfully started
s6-rc: info: service adguard: starting
s6-rc: info: service adguard successfully started
s6-rc: info: service discovery: starting
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
[00:30:56] INFO: Starting AdGuard Home server...
2023/02/01 00:30:57.217073 [info] AdGuard Home, version v0.107.22
2023/02/01 00:30:57.218238 [info] AdGuard Home updates are disabled
2023/02/01 00:30:57.248254 [info] tls: using default ciphers
2023/02/01 00:30:57.276063 [info] dhcp: loaded leases v4:71 v6:0 total-read:71 from DB
2023/02/01 00:30:57.319108 [info] Initializing auth module: /data/adguard/data/sessions.db
2023/02/01 00:30:57.320577 [info] auth: initialized. users:0 sessions:0
2023/02/01 00:30:57.320604 [info] web: initializing
2023/02/01 00:30:57.661859 [info] dnsproxy: cache: enabled, size 4096 b
2023/02/01 00:30:57.661898 [info] MaxGoroutines is set to 300
2023/02/01 00:30:57.663189 [info] dhcpv4: listening
2023/02/01 00:30:57.664592 [info] AdGuard Home is available at the following addresses:
2023/02/01 00:30:57.665077 [info] Go to http://127.0.0.1:45158
[dhcpv4] 2023/02/01 00:30:57 Server listening on 0.0.0.0:67
[dhcpv4] 2023/02/01 00:30:57 Ready to handle requests
[00:30:57] INFO: Starting NGinx...
[00:30:58] DEBUG: Requested API resource: http://supervisor/discovery
[00:30:58] DEBUG: Request method: POST
[00:30:58] DEBUG: Request data: {"service":"adguard","config":{"host":"127.0.0.1","port":45158}}
[00:30:58] DEBUG: API HTTP Response code: 200
[00:30:58] DEBUG: API Response: {"result": "ok", "data": {"uuid": "29fed5ee90154ab5af811c4a14bb1b24"}}
[00:31:00] DEBUG: Filtering response using: .uuid
[00:31:02] INFO: Successfully send discovery information to Home Assistant.
s6-rc: info: service discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2023/02/01 00:31:03.136097 [info] Starting the DNS proxy server
2023/02/01 00:31:03.144272 [info] Ratelimit is enabled and set to 20 rps
2023/02/01 00:31:03.147621 [info] The server is configured to refuse ANY requests
2023/02/01 00:31:03.148482 [info] dnsproxy: cache: enabled, size 4194304 b
2023/02/01 00:31:03.149099 [info] MaxGoroutines is set to 300
2023/02/01 00:31:03.149657 [info] Creating the UDP server socket
2023/02/01 00:31:03.150506 [info] Listening to udp://192.168.1.10:53
2023/02/01 00:31:03.150705 [info] Creating the UDP server socket
2023/02/01 00:31:03.151504 [info] Listening to udp://172.30.32.1:53
2023/02/01 00:31:03.152114 [info] Creating the UDP server socket
2023/02/01 00:31:03.152882 [info] Listening to udp://127.0.0.1:53
2023/02/01 00:31:03.153489 [info] Creating the UDP server socket
2023/02/01 00:31:03.153846 [info] Listening to udp://[::1]:53
2023/02/01 00:31:03.154384 [info] Creating a TCP server socket
2023/02/01 00:31:03.155224 [info] Listening to tcp://192.168.1.10:53
2023/02/01 00:31:03.155823 [info] Creating a TCP server socket
2023/02/01 00:31:03.156482 [info] Listening to tcp://172.30.32.1:53
2023/02/01 00:31:03.159616 [info] Creating a TCP server socket
2023/02/01 00:31:03.160395 [info] Listening to tcp://127.0.0.1:53
2023/02/01 00:31:03.161092 [info] Creating a TCP server socket
2023/02/01 00:31:03.161698 [info] Listening to tcp://[::1]:53
2023/02/01 00:31:03.162537 [info] Entering the tcp listener loop on 192.168.1.10:53
2023/02/01 00:31:03.163092 [info] Entering the UDP listener loop on 192.168.1.10:53
2023/02/01 00:31:03.163664 [info] Entering the UDP listener loop on 172.30.32.1:53
2023/02/01 00:31:03.166487 [info] Entering the UDP listener loop on 127.0.0.1:53
2023/02/01 00:31:03.167243 [info] Entering the UDP listener loop on [::1]:53
2023/02/01 00:31:03.167957 [info] Entering the tcp listener loop on [::1]:53
2023/02/01 00:31:03.168454 [info] Entering the tcp listener loop on 172.30.32.1:53
2023/02/01 00:31:03.169105 [info] Entering the tcp listener loop on 127.0.0.1:53
[dhcpv4] 2023/02/01 00:31:05 Handling request from 0.0.0.0:68
2023/02/01 00:31:05.492059 [info] dhcp: stored 71 leases in db
[dhcpv4] 2023/02/01 00:40:57 Handling request from 192.168.1.244:68
[dhcpv4] 2023/02/01 00:41:00 Handling request from 0.0.0.0:68
2023/02/01 00:41:00.128076 [info] dhcp: stored 71 leases in db
[dhcpv4] 2023/02/01 00:41:00 Handling request from 0.0.0.0:68
2023/02/01 00:41:00.153895 [info] dhcp: stored 71 leases in db
[dhcpv4] 2023/02/01 00:51:25 Handling request from 0.0.0.0:68
2023/02/01 00:51:25.972652 [info] dhcp: stored 71 leases in db

[Bellavista]

I can't find the solution, I reinstalled from 0 ADguard....no result