https://bugzilla.redhat.com/show_bug.cgi?id=1096280

            Bug ID: 1096280
           Summary: docker top stopped working, cgroup path changed
           Product: Red Hat Enterprise Linux 7
           Version: 7.1
         Component: docker
          Assignee: [email protected]
          Reporter: [email protected]
        QA Contact: [email protected]
                CC: [email protected], [email protected],
                    [email protected], [email protected],
                    [email protected], [email protected],
                    [email protected]
        Depends On: 1088125



+++ 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


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1088125
[Bug 1088125] docker top stopped working, cgroup path changed
-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
golang mailing list
[email protected]
https://lists.fedoraproject.org/mailman/listinfo/golang

Reply via email to