Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • If your Docker host is CentOS 7.4+, then I believe you are affected by the default TasksMax attribute of systemd (I saw that it is enabled from this bug report). Add TasksMax=infinity to your Docker service file override and see if it helps or prints the warning that it is not available. Commented Apr 25, 2019 at 19:13
  • Hi @GracefulRestart: my system is not affected by that; since I have systemd = 219 which does not have the TasksMax parameter; as noted in my question. Commented Apr 25, 2019 at 19:14
  • If you are on CentOS 7.4 or higher, then you are affected by it as it was backported to systemd-219-42 as per this errata announcement. Commented Apr 25, 2019 at 19:29
  • I have centos 7.6, systemd 219-62 but yet when I run systemctl status docker it says Tasks: 135 and there is no maximum between brackets so I still think that this is not the reason. Also my limit seems to lie at 4096 threads and not at 512. Commented Apr 25, 2019 at 19:45