-
Notifications
You must be signed in to change notification settings - Fork 655
Cannot run docker top
on user containers.
#2340
Comments
Exactly same problem for me, just wanted to add an issue for this as well. Also I just noted, that this is a problem with the Edit: |
Nice catch! I can confirm that I was using the |
If anyone would like a workaround:
|
This has been fixed in ROS v1.4.0.
|
@niusmallnan looks that this issue still exists on v1.4.1 😢 |
Reopen it, I may miss something. |
I verified all consoles and |
RancherOS Version: (ros os version) v1.3.0
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.) bare metal
It is not possible to run
docker top
to see what processes are running inside a non-system container.Note that I can successfully run
sudo system-docker top docker
, which implies that there's aps
executable available to the system, but not to user-docker.This makes it so that my Jenkins pipelines (that I'm trying to move to this new ROS box) will not be able to run their
docker.image().inside {}
steps. (Jenkins is using this container start withcat
, usingtop
to check that it started, and then running commands in this container withexec
calls.)The text was updated successfully, but these errors were encountered: