Conversation
Added a new section explaining how to resolve the common inotify instance limit error on Linux and Docker by increasing fs.inotify.max_user_instances and max_user_watches via sysctl. Fixes dotnet#19814 Signed-off-by: Yusuf Baylav <330015149+baylavdev@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The guidance conflates distinct failure modes and recommends globally aggressive limits without sufficient qualification.
Get a fresh assessment by requesting another Copilot review.
Review effort: Lite
Findings: 1
Open (2)
What changed in this PR
Adds Linux inotify-limit troubleshooting guidance to the dotnet watch tutorial.
Changes:
- Documents temporary and permanent
sysctlconfiguration. - Explains Docker host-limit inheritance.
| File | Description |
|---|---|
aspnetcore/tutorials/dotnet-watch.md |
Adds Linux file-watcher troubleshooting guidance. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| `The configured user limit (128) on the number of inotify instances has been reached, or the per-process limit on the number of open file descriptors has been reached.` | ||
|
|
||
| This happens because the operating system limits the number of file watchers that a single user can create. To resolve this issue, increase the `fs.inotify.max_user_instances` and `fs.inotify.max_user_watches` system limits. |
| * Switch to a different terminal, such as https://github.com/microsoft/terminal, that supports rendering non-ASCII characters. | ||
|
|
||
|
|
||
| ## File watcher limits in Linux |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a dedicated troubleshooting and configuration section for Linux inotify file watcher limits in dotnet/tutorials/dotnet-watch.md.
Why
Fixes #19814. Developers running dotnet watch on Linux or inside Docker containers frequently encounter the The configured user limit (128) on the number of inotify instances has been reached error when handling multiple projects or high-frequency file changes. Documenting how to adjust fs.inotify.max_user_instances and fs.inotify.max_user_watches via sysctl prevents recurring friction.
How
Appended a new section detailing temporary (sysctl) and permanent (/etc/sysctl.conf) configuration steps.
Added a clear note explaining that Docker containers inherit these limits from the host operating system.
Internal previews
Build report