Closed Gprsk closed 4 years ago
@Gprsk do you have any other containers running on the same node? Did you try any of the mitigations/etc. described in https://github.com/dotnet/aspnetcore/issues/7531 ? Yes, they are on 2.1, but I don't think there's been any change in 3.1 that would change our behavior. The inotify
limits are per-user and configured on the host machine (i.e. the node) rather than the container, so if you have a significant number of containers running on the same node this problem could be exasperated.
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.
See our Issue Management Policies for more information.
I've been getting this issue regularly when using Docker on a Kubernetes deployment. Code did not change, but after a while we are unable to start new containers because they keep crashing.
My setup code is as simple as it can be:
Startup class is quite simple:
To Reproduce
Just start my project
Exception message:
Further technical details
Running Docker/Kubernetes on Ubuntu 18 / Alpine
I've seen the same error on other issues (#8449, #11038, #7531) but they all are on 2.1, currently im running version 3.1.