Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Error: watch ENOSPC on 0.15 (running inside Docker)
See original GitHub issueI can no longer use forever inside Docker container after updating to 0.15. I have plenty of space left, not sure why I’m getting ENOSPC.
Rolling back to 0.14.2 works.
Jul 29 14:23:34 coreos docker[12137]: events.js:85
Jul 29 14:23:34 coreos docker[12137]: throw er; // Unhandled 'error' event
Jul 29 14:23:34 coreos docker[12137]: ^
Jul 29 14:23:34 coreos docker[12137]: Error: watch ENOSPC
Jul 29 14:23:34 coreos docker[12137]: at exports._errnoException (util.js:746:11)
Jul 29 14:23:34 coreos docker[12137]: at FSWatcher.start (fs.js:1172:11)
Jul 29 14:23:34 coreos docker[12137]: at Object.fs.watch (fs.js:1198:11)
Jul 29 14:23:34 coreos docker[12137]: at createFsWatchInstance (/usr/src/app/node_modules/forever/node_modules/forever-monitor/node_modules/chokidar/lib/nodefs-handler.js:37:15)
Jul 29 14:23:34 coreos docker[12137]: at setFsWatchListener (/usr/src/app/node_modules/forever/node_modules/forever-monitor/node_modules/chokidar/lib/nodefs-handler.js:80:15)
Jul 29 14:23:34 coreos docker[12137]: at EventEmitter.NodeFsHandler._watchWithNodeFs (/usr/src/app/node_modules/forever/node_modules/forever-monitor/node_modules/chokidar/lib/nodefs-handler.js:228:14)
Jul 29 14:23:34 coreos docker[12137]: at EventEmitter.NodeFsHandler._handleFile (/usr/src/app/node_modules/forever/node_modules/forever-monitor/node_modules/chokidar/lib/nodefs-handler.js:255:21)
Jul 29 14:23:34 coreos docker[12137]: at EventEmitter.<anonymous> (/usr/src/app/node_modules/forever/node_modules/forever-monitor/node_modules/chokidar/lib/nodefs-handler.js:468:21)
Jul 29 14:23:34 coreos docker[12137]: at FSReqWrap.oncomplete (fs.js:95:15)
Issue Analytics
- State:
- Created 8 years ago
- Reactions:2
- Comments:17 (4 by maintainers)
Top Results From Across the Web
Error: watch ENOSPC on 0.15 (running inside Docker ... - GitHub
I can no longer use forever inside Docker container after updating to 0.15. I have plenty of space left, not sure why I'm...
Read more >Developers - Error: watch ENOSPC on 0.15 (running inside Docker) -
I can no longer use forever inside Docker container after updating to 0.15. I have plenty of space left, not sure why I'm...
Read more >Node.js: what is ENOSPC error and how to solve?
"Visual Studio Code is unable to watch for file changes in this large workspace" (error ENOSPC). It indicates that the VS Code file...
Read more >Need To Solve: ENOSPC: no space left on device
My suggestion: Try to run the commands in an interactive shell in a container instead of running Docker build. Then you can see...
Read more >Configure ksqlDB with Docker
Assign configuration settings in the Docker run command¶. You can pass configuration settings dynamically into containers by using environment ...
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
Has anyone here tried upping the number of inotify watchers? You have to do it inside of the host, and then the docker container will have the same number. You can’t modify this value from inside the docker container for security reasons AFAIK.
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -pIn https://github.com/facebook/jest/issues/3254 @maraisr did some research for another problem.
There’s also a great post here if you want to know how to see your current inotify watcher value, and see how many are being used at any given time.
https://unix.stackexchange.com/questions/13751/kernel-inotify-watch-limit-reached
WTF… it’s watching everything, even without
--watchDirectory, are you kidding?