Increase fs.inotify.max_user_watches in docker container
See original GitHub issueOpening certain projects leads to this error. However I am not sure how to work around it within the container. I have tried simply mounting a modified /etc/sysctl.conf
from my host but it doesn’t seem to make a difference.
How can we increase this within the container?
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Increase fs.inotify.max_user_watches in docker container #628
I have tried simply mounting a modified /etc/sysctl.conf from my host but it doesn't seem to make a difference. How can we increase...
Read more >Changing fs.inotify.max_user_watches - Build Environment
Since inotify limits cannot be raised in the Circle 2.0 docker, I've gotten successful builds (and deploys with exp publish ) by using...
Read more >Increase watchers in node docker image - Stack Overflow
You need to increase the fs.inotify.max_user_watchesparameter on the host. For example you can create a configuration file in /etc/sysctl.d.
Read more >inotify limit in docker container : r/jellyfin - Reddit
Hi, I am running jellyfin on a docker container and get the error ... -How-to-increase-the-inotify-max-user-watches-and-inotify-max-user- ...
Read more >Add fs.inotify.max_user_watches to supported sysctls
* are allowed to be passed via docker run --sysctl <option>=<value> ... For building larger ReactNative-Apps, it is necessary to set/increase fs ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I resolved by running the command on docker host machine:
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf
sudo sysctl -p
Success, thanks!
@perguth Docker mounts
/proc
as read-only since many of its knobs are global.If you run that same command on the host, the container will transparently inherit the new setting.