Bug 1329904

Summary: top command doesn't output any processes
Product: [Fedora] Fedora Reporter: Tomas Tomecek <ttomecek>
Component: dockerAssignee: Antonio Murdaca <amurdaca>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 25CC: adimania, admiller, amurdaca, dwalsh, ichavero, jcajka, jchaloup, lsm5, marianne, miminar, mpatel, nalin, riek, vbatts
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1362691 (view as bug list) Environment:
Last Closed: 2017-12-12 10:48:48 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: 1362691    

Description Tomas Tomecek 2016-04-24 16:48:09 UTC
Version-Release number of selected component (if applicable):

docker-1.11-5.git69e6294.fc25.x86_64


I have this container:

$ docker run -d fedora bash -c "while : ; do date ; sleep 1 ; done"


When I perform top command on this container I get this:

$ docker top 3bb88339a0a036354a2dd0b625131c7a2a184d9190a8d90f36ecd58590edde5d
UID                 PID                 PPID                C                   STIME               TTY                 TIME                CMD

I would expect two processes there: bash and sleep.


Verbose debug logs:

Apr 24 18:39:28 oat docker[26470]: time="2016-04-24T18:39:28.482975576+02:00" level=info msg="{Action=top, ID=3bb88339a0a036354a2dd0b625131c7a2a184d9190a8d90f36ecd58590edde5d, LoginUID unknown, PID unknown}"
Apr 24 18:39:28 oat docker[26470]: time="2016-04-24T18:39:28.483056555+02:00" level=debug msg="Calling GET /v1.23/containers/cucoslib-data/top"

Comment 1 Antonio Murdaca 2016-04-26 15:08:30 UTC
cannot reproduce using 1.11 on F23 - will update after testing on fedora - there are some issues with selinux right now when installing 1.11 in rawhide though, might (?) be related if I can reproduce

Comment 2 Antonio Murdaca 2016-04-26 15:27:17 UTC
Reproduced, no clue about what's happening will investigate

Comment 3 Tomas Tomecek 2016-04-27 08:07:51 UTC
just for the record, my selinux is disabled (I'm sorry)

It's interesting why docker is not able to locate the processes within container -- not sure if it's using ps binary or there is some implementation of ps in go; also, it may be worth reproduce with upstream git master, haven't tried that

Comment 4 Antonio Murdaca 2016-04-27 08:17:55 UTC
Upstream master seems to be working fine, I've pushed another Rawhide docker update to test it out though. My guess is that the pid isn't found for some reason. No daemon logs also. I'll continue investigating.

Comment 5 Daniel Walsh 2016-04-27 12:03:57 UTC
Might be a cgroup issue. BTW I am fixing the SELinux issues with docker in Rawhide.  Should be able to enable it again soon.

Comment 6 Antonio Murdaca 2016-04-27 12:23:41 UTC
Yup, Mrunal any idea?

Comment 7 Mrunal Patel 2016-04-28 22:18:46 UTC
The issue is that containerd is hard coded to use cgroupfs to get the pids whereas we use systemd cgroups support. This was fixed upstream a couple of days ago. However, there is no way I can backport it without our own forks of containerd. We need to set that up.

Comment 8 Daniel Walsh 2016-04-29 19:06:36 UTC
I guess we will have to carry a patched version of containerd then.

Comment 9 Daniel Walsh 2016-06-03 20:04:28 UTC
Is this fixed in latest docker-1.12 code?

Comment 10 Antonio Murdaca 2016-06-06 10:38:21 UTC
Yes, this https://github.com/docker/containerd/commit/c2df6e08cf6d06b194b31b2bc9778f5f0b30d198 and the associated runc changes are in 1.12-dev (but we still need to setup 1.12-dev in Rawhide)

Comment 11 Jan Kurik 2016-07-26 04:04:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.

Comment 12 Fedora End Of Life 2017-11-16 19:15:17 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 13 Fedora End Of Life 2017-12-12 10:48:48 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.