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 1385924 - docker run --cgroup-parent : unexpected result for pid
Summary: docker run --cgroup-parent : unexpected result for pid
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: docker
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Matthew Heon
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-17 21:57 UTC by Ed Santiago
Modified: 2019-03-06 01:02 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-17 20:43:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:0116 0 normal SHIPPED_LIVE Moderate: docker security, bug fix, and enhancement update 2017-01-18 01:39:43 UTC

Description Ed Santiago 2016-10-17 21:57:16 UTC
docker-autotest reporting this failure on docker-1.10.3-55.el7.x86_64 et al:

    # docker run --rm --cgroup-parent=foo-bar.slice centos cat /proc/1/cgroup
    11:perf_event:/foo.slice/foo-bar.slice/docker-<sha>.scope
    ...
    5:cpuacct,cpu:/foo.slice/foo-bar.slice/docker-<sha>.scope
 >> 4:pids:/
    3:cpuset:/foo.slice/foo-bar.slice/docker-<sha>.scope
    ...

Comment 2 Mrunal Patel 2016-10-18 17:51:03 UTC
What OS are you testing on? I do not see the pids cgroup enabled on my RHEL 7.2 VM.

Comment 3 Ed Santiago 2016-10-18 17:58:53 UTC
RHEL 7.3, kernel 3.10.0-513.el7.x86_64

Comment 4 Mrunal Patel 2016-10-18 18:06:12 UTC
Thanks! I checked the code. We don't have the pids cgroups support for libcontainer in our docker 1.10.x branches. So, if we really want it in docker 1.10 then we need a backport which should be straight forward. 

Dan, wdyt about backporting to 1.10 or should we just support it in 1.12+?

Comment 5 Daniel Walsh 2016-10-18 18:33:08 UTC
I think we should just support this in docker-1.12 unless we are forced by OpenShift.  For now lets close this as fixed in docker-1.12.

Comment 7 Luwen Su 2016-11-12 09:08:48 UTC
In docker-1.12.3-4.el7.x86_64

# docker run --rm --cgroup-parent=foo-bar.slice rhel7 cat /proc/1/cgroup
.....
10:pids:/foo.slice/foo-bar.slice/docker-9788efa1b06cfa3dd86ad523c79dde6143740908b030d434fbeda03939b7365d.scope

Comment 9 errata-xmlrpc 2017-01-17 20:43:32 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.

https://rhn.redhat.com/errata/RHSA-2017-0116.html


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