Debugging 'Too many open files' in Kubernetes: nofile vs inotify/fsnotify
· 5 min read
When you see too many open files in a containerized app, it’s tempting to jump straight to ulimit -n. Sometimes that’s correct. But on Linux (especially with Go apps using fsnotify), the error can also be caused by inotify limits—even if your process has a huge file-descriptor limit.
This post is a practical, copy/paste-friendly checklist to debug the problem on a real Kubernetes cluster.