Open gz opened 6 years ago
This issue depends from the new systemd behavior, look at this issue
We were aware of the TasksMax issue at the time and set it to infinity. However, it didn't resolve the issue.
might be linked to this: https://github.com/docker/for-linux/issues/654
We're trying to spawn a large amount of small docker containers on our server machines (the memory footprint is around 10 MiB). However, when doing so, docker crashes after spawning approx. 400 instances with the following error message:
We were unable to pinpoint the exact resource limit for this. We still have more than enough memory available in the system (~100 GiB) and the typical limits we checked are set high enough i.e.:
A different machine with a more recent kernel version 4.15 allowed us to spawn ~4k containers but failed with the same error long before running out of memory.
The same issue is discussed here but the proposed fixes did not resolve the problem for us: https://github.com/moby/moby/issues/9868
I realize this may not directly be a docker problem but is it possible to tell what other limit I'm encountering that prevents from spawning more containers?
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.)