AdguardTeam
[fatal] initing hosts container: hosts container: adding path: os watcher: no space left on device
Prerequisites
-
[X] I have checked the Wiki and Discussions and found no answer
-
[X] I have searched other issues and found no duplicates
-
[X] I want to report a bug and not ask a question or ask for help
-
[X] I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Custom (please mention in the description)
Installation
Docker
Setup
On one machine
AdGuard Home version
latest (v0.107.39)
Action
My host is a Synology DS918+ where I have 40 containers and no problem with them... Only with ADGuard : I create my docker compose like you suggest (file attached) docker-compose.yaml.txt
I can setup adguard, and login me.
If I restart my Adguard Container , It's broken like I have disk full, but really, I have more 4To free.
Log of my Portainer in attached file : Log Portainer AdGuard.txt
I can't understand why I can restart all my containers but only one Crash (AdGuard)
Expected result
I check on Internet, some forums, your discord, and I find a command to purge come cache on Synology
sudo docker system prune -a
but that no change the result :-(
Actual result
I can work with adguard but I mustn't restart it
Additional information and/or screenshots
No response
This doesn't seem to be an issue related to AdGuard Home. You can try workaround this by setting clients.runtime_sources.hosts to false, but you should probably inspect your Docker setup.
Might be unrelated: Have you tried to normally setup & manage the docker container through Container Manager on Synology Web UI?
This doesn't seem to be an issue related to AdGuard Home. You can try workaround this by setting
clients.runtime_sources.hoststofalse, but you should probably inspect your Docker setup.
It doesn't help in my case
I'm using Synology DS923+ and Container Manager. AdGuard from official channel. It works until reboot. After that I've got the same error. The issue is only with AdGuard. I tried docker with PiHole and it works.
I'm using Synology DS923+ and Container Manager. AdGuard from official channel. It works until reboot. After that I've got the same error. The issue is only with AdGuard. I tried docker with PiHole and it works.我使用的是 Synology DS923+ 和 Container Manager。AdGuard 来自官方渠道。在重启之前一直正常。重启后，我又遇到了同样的错误。问题只出在 AdGuard 上。我试过使用 PiHole 的 docker，可以正常运行。
Did you solve it? I have the same problem.
Based on the input from here https://github.com/AdguardTeam/AdGuardHome/issues/7596#issuecomment-2727019475 I made the following changes and it is now working again
Stop the running adguard docker container.
SSH into the NAS and run the following: sudo sysctl -w fs.inotify.max_user_watches=524288
Make the change permanent by adding the following line to /etc/sysctl.conf: fs.inotify.max_user_watches=524288
Finally, apply the change by running the following: sudo sysctl -p
Based on the input from here #7596 (comment) I made the following changes and it is now working again
Stop the running adguard docker container.
SSH into the NAS and run the following: sudo sysctl -w fs.inotify.max_user_watches=524288
Make the change permanent by adding the following line to /etc/sysctl.conf: fs.inotify.max_user_watches=524288
Finally, apply the change by running the following: sudo sysctl -p
Thank you. Problem solved