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 #1088125 +++
Description of problem:
The `docker top` command stopped working, the path to cgroup processes had changed.
Version-Release number of selected component (if applicable):
docker-0.10.0-8.el7.x86_64
docker-io-0.10.0-2.fc20.x86_64
How reproducible:
always
Steps to Reproduce:
1. docker run -i fedora bash
2. docker top $NAME
Actual results:
[root@t530 ~]# docker top determined_jones
2014/04/16 07:47:52 Error: open /sys/fs/cgroup/devices/system.slice/docker/93dfbd4d375cf026df215d87b5d93de8b0a9bd55094e33c2ca3322cd6afb53f1/tasks: no such file or directory
Expected results:
list of processes...
Additional info:
[root@t530 ~]# ls /sys/fs/cgroup/devices/system.slice/
cgroup.clone_children
cgroup.event_control
cgroup.procs
devices.allow
devices.deny
devices.list
docker-93dfbd4d375cf026df215d87b5d93de8b0a9bd55094e33c2ca3322cd6afb53f1.scope
notify_on_release
tasks
--- Additional comment from Lukas Doktor on 2014-05-05 03:46:55 EDT ---
The same bug is in upstream Docker version 0.10.0, build dc9c28f/0.10.0
The difference between Fedora and RHEL problem is, that RHEL tries to access:
docker top test_eoly
2014/05/09 16:56:22 Error: open /sys/fs/cgroup/devices/docker-d6dec8258b30eaecaa96f6110a427d4c3bf40fe8ec03b91ed4f277f3d835c23c.scope/tasks: no such file or directory
And the directories are:
[root@t530 ~]# ls /sys/fs/cgroup/devices/system.slice/
cgroup.clone_children
cgroup.procs
devices.allow
devices.deny
devices.list
docker-d6dec8258b30eaecaa96f6110a427d4c3bf40fe8ec03b91ed4f277f3d835c23c.scope
notify_on_release
tasks
Note that this was executed on Fedora 20 with docker from collider, so the path problem might be incorrect. I'll retest this directly on RHEL later.
Retested on RHEL-7.0-20140507.0 with the same error:
[root@cisco-b200m1-04 ~]# docker top elegant_bohr
2014/05/09 12:09:06 Error: open /sys/fs/cgroup/devices/docker-a1c00b36178aaa4bd35a1aa60a8707569dd65ffcc1c6168f9af084779846af9a.scope/tasks: no such file or directory
[root@cisco-b200m1-04 ~]# ls /sys/fs/cgroup/devices/system.slice/
cgroup.clone_children cgroup.procs devices.deny docker-a1c00b36178aaa4bd35a1aa60a8707569dd65ffcc1c6168f9af084779846af9a.scope tasks
cgroup.event_control devices.allow devices.list notify_on_release
[root@cisco-b200m1-04 ~]# ls /sys/fs/cgroup/devices
cgroup.clone_children cgroup.event_control cgroup.procs cgroup.sane_behavior devices.allow devices.deny devices.list notify_on_release release_agent system.slice tasks
Hi Daniel, Chris tested it successfully on docker-0.11.1-2.el7.x86_64. I tried docker-0.11.1-3.el7.x86_64 and today's the docker-0.11.1-5.el7.x86_64 and booth are failing. Did the patch slipped away?