New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to create more than 200 containers by default #726
Milestone
Comments
@dhiltgen have you tried containerd?. Seems to me like runC is already battle tested. |
I was using docker 1.11.0-rc3 |
This was referenced May 20, 2016
This is being fixed in the upper layers. There is not much we should do at this layer. |
@dhiltgen you can follow the progress for the change in docker here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you attempt to create more than 200 containers, you get a rather confusing error message from the daemon.
It appears that #582 coupled with the default
/proc/sys/kernel/keys/
quota leads to this.Ideally users shouldn't have to modify this by hand to run more than 200 containers on the system.
The text was updated successfully, but these errors were encountered: