Bug 1660876

Summary: Docker needs to support PIDs Limit for all containers created.
Product: Red Hat Enterprise Linux 7 Reporter: Daniel Walsh <dwalsh>
Component: dockerAssignee: Lokesh Mandvekar <lsm5>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: amurdaca, dornelas, dwalsh, fkluknav, lrock, lsm5, lsu, mpatel, pasik, sfowler, sreber
Target Milestone: rcKeywords: Extras
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: docker-1.13.1-92.gitb2f74b2.el7 Doc Type: Enhancement
Doc Text:
Added to help prevent fork bomb attacks in containers.
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-03-13 01:52:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1186913, 1647729    

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.