Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47872 - [docker] Increase TasksMax in docker.service
Attached to Project:
Community Packages
Opened by Candid Dauth (cdauth) - Saturday, 23 January 2016, 15:24 GMT
Last edited by Sébastien Luttringer (seblu) - Friday, 05 February 2016, 19:58 GMT
Opened by Candid Dauth (cdauth) - Saturday, 23 January 2016, 15:24 GMT
Last edited by Sébastien Luttringer (seblu) - Friday, 05 February 2016, 19:58 GMT
|
Detailssystemd 228 introduces a new directive TasksMax (http://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#TasksAccounting=) when running on kernel 4.3 or higher (with cgroup pid subsystem enabled). It limits the number of processes and threads that a particular service can start and defaults to 512.
Reaching this limit will cause the docker daemon or programs running within containers to crash with "Resource temporarily unavailable" when attempting to create a thread or to fork. The limit should be greatly increased, as docker typically runs many programs. The example systemd files provided with docker have been adjusted in this pull request: https://github.com/docker/docker/pull/19391 The docker.service file provided with the Arch docker package should be adjusted as well by adding TasksMax=1048576. |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Friday, 05 February 2016, 19:58 GMT
Reason for closing: Fixed
Friday, 05 February 2016, 19:58 GMT
Reason for closing: Fixed
Comment by Candid Dauth (cdauth) -
Saturday, 23 January 2016, 15:35 GMT
More details regarding this issue can be found here: http://unix.stackexchange.com/a/255603/59955