RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1660876 - Docker needs to support PIDs Limit for all containers created.
Summary: Docker needs to support PIDs Limit for all containers created.
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
Depends On:
Blocks: 1186913 1647729
TreeView+ depends on / blocked
Reported: 2018-12-19 13:30 UTC by Daniel Walsh
Modified: 2020-09-21 08:19 UTC (History)
11 users (show)

Fixed In Version: docker-1.13.1-92.gitb2f74b2.el7
Doc Type: Enhancement
Doc Text:
Added to help prevent fork bomb attacks in containers.
Clone Of:
Last Closed: 2019-03-13 01:52:23 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Article) 3979541 0 None None None 2019-03-12 08:21:29 UTC
Red Hat Product Errata RHSA-2019:0487 0 None None None 2019-03-13 01:52:49 UTC

Description Daniel Walsh 2018-12-19 13:30:04 UTC
In order to prevent accidental fork bombs we need to add a new docker daemon option to set the default maximum number of processes within a container.  This max number should then be set in the cgroups created for each container.

Comment 5 Antonio Murdaca 2018-12-19 16:44:17 UTC
PR for docker here https://github.com/projectatomic/docker/pull/333

Comment 11 Antonio Murdaca 2019-01-11 10:57:56 UTC
The fix for 1.12 isn't merged as I believe there's no path forward to ship a docker 1.12 at all. The PR for 1.12 is still here: https://github.com/projectatomic/docker/pull/334

Assuming this blocker BZ is just for 1.13, this is in POST so we just need to rebuild docker wherever necessary. CC'ing Lokesh. Let me know if we need to merge and ship the 1.12 fix (even if I would strongly discourage shipping such a feature to such an old package).

Comment 18 errata-xmlrpc 2019-03-13 01:52:23 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.