Open alxbl opened 2 months ago
AdGuard-Home deployment won't start anymore because of inotify.
https://stackoverflow.com/a/63700455 https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files https://github.com/kubernetes-sigs/kind/issues/2586 https://superuser.com/questions/1779937/whats-the-maximum-safe-limit-for-fs-inotify-max-user-watches
This works:
# On the host sudo sysctl fs.inotify.max_user_watches=524288 sudo sysctl fs.inotify.max_user_instances=512
But it needs to be made permanent as part of node provisioning.
It's actually because adguard shares the same uid as jelly fin (https://github.com/jellyfin/jellyfin/issues/7684)
Possible fixes:
Hopefully fixed by 9acd4f4
AdGuard-Home deployment won't start anymore because of inotify.
https://stackoverflow.com/a/63700455 https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files https://github.com/kubernetes-sigs/kind/issues/2586 https://superuser.com/questions/1779937/whats-the-maximum-safe-limit-for-fs-inotify-max-user-watches
This works:
But it needs to be made permanent as part of node provisioning.