Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

+++ This bug was initially created as a clone of Bug #1329904 +++

...just setting a placeholder to make sure this gets fixed in RHEL.

Same issue in docker-1.12.0-6.el7:

    # cid=$(docker run --detach fedora sleep 5m)
    # docker top $cid -auxww
    USER                PID                 %CPU                %MEM                VSZ                 RSS                 TTY                 STAT                START               TIME                COMMAND

(note no actual process lines). Fix is upstream; see bug 1329904 for details.

Runcom can we get this fix into our package?

The code is fixed both upstream and in our projectatomic/docker. This is probably a misconfig of the unit files.
I did some fixes to the fedora rawhide docker.spec and the command in this BZ is working fine. Lokesh can you port those fixes to RHEL?

Lokesh should this be in the modified state?

I have run O(50) iterations of docker-autotest on docker-latest-1.12.0-9.el7, and two quick runs on docker-latest.1.12.0-10.el7, and have not seen this problem recur.

Cannot reproduce on docker-latest-1.12.1-2.el7 over many, many runs. Calling it fixed.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.