-
-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Silent fail when fs.inotify.max_user_watches is exceeded #46
Comments
I ran into this as well, but in the context of webpack HMR, where this leads webpack into a state where it's watching some files but not others. This was extremely frustrating and time-consuming to track down. I'm happy to try to contribute a patch with some guidance. Any suggestions as to where to start? And is the particular issue that I ran into a watchpack or webpack problem? |
Hey, I ran into a probably similar problem for macos. Running watch in directories that have symlinks doesn't do anything. The directories to be watched are correct but changing files in that directories doesn't trigger any new build. Could be this related to macos watchers configuration or watchpack/chokidar? |
Docker container configuration
Host configuration
Issue
Running
webpack --watch
in docker container successfully performs one build and then exits with exit code 0 (success).Expectation
Some kind of error code and a return code != 0 if max_user_watches is exceeded.
Workaround
Increasing
/proc/sys/fs/inotify/max_user_watches
on the host system fixes the problem.Moved from webpack/webpack#1281
The text was updated successfully, but these errors were encountered: