-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Dot Net Core devcontainer without "The configured user limit (128) on the number of inotify instances has been reached" #418
Comments
This is a great suggestion. Happy to take a PR if you've got one, otherwise we'll add this to the queue to pick up! |
Thanks @Chuxel - I'd love to contribute a PR but try as I might I haven't succeeded in resolving this myself. I thought raising the issue here might help to surface one from a kind soul with the answer 😉 So if you, @paillave or anyone else is able to help when you get a chance I'd greatly appreciate it. (And looking at the linked issues I'd say I'm not alone in that!) cc @travisgosselin who is bumping on this too: |
Just to share ideas that I've come upon (but don't seem to be able to get working):
I tried marrying this with |
Same issue here on some of the containers. I can't figure out why some of them work others don't. This only happens when usin "Open Repository in a Container" feature. |
Just a side note: this is tagged as |
I use the dotnetcore devcontainer and it's wonderful! Thanks so much for putting it together!
I have one problem with the container. I often experience the famous "The configured user limit (128) on the number of inotify instances has been reached" issue, particularly when running tests. This doesn't seem to a well solved problem in the dot net core space.
@paillave has suggested a workaround:
Is there a way we could apply the suggestion here to the dotnetcore devcontainer image? That way, anyone using the dotnetcore devcontainer wouldn't bump on this issue.
dotnet/aspnetcore#7531
dotnet/aspnetcore#8449
https://github.com/dotnet/aspnetcore/issues/21838
I should say that it would be tremendous if the problem was directly solved in dot net core, but I'll take a workaround when I have one!
The text was updated successfully, but these errors were encountered: