News for hackers. Stuff that matters.
Re:Ctop – commandline monitoring for containers by brunoqc on Thursday March 09, 2017 @04:26PM (#13833859)
Isn't it recommended to not make Docker listen on the TCP port?
Re:Ctop – commandline monitoring for containers by raesene9 on Thursday March 09, 2017 @05:16PM (#13834326)
From reading the docs, it looks like ctop will connect to the local UNIX socket if there's no environment variable specifying a host, so you don't need to expose a TCP port to get this working.
Re:Ctop – commandline monitoring for containers by andrewguenther on Thursday March 09, 2017 @04:51PM (#13834086)
You should always use a UNIX socket if you don't need remote access.
Re:Ctop – commandline monitoring for containers by noinsight on Thursday March 09, 2017 @07:28PM (#13835235)
SSH supports forwarding UNIX sockets...
Re:Ctop – commandline monitoring for containers by andrewguenther on Tuesday March 14, 2017 @01:30AM (#13865254)
Would not recommend
Re:Ctop – commandline monitoring for containers by zenlikethat on Thursday March 09, 2017 @07:02PM (#13835064)
Yes. Otherwise any process which can access the TCP port has full root access on the computer where Docker is installed. And root access to the entire Docker swarm cluster if swarm mode is enabled and the current node is acting as a manager.

Whether or not giving root access to a system performance tool is wise is left as an exercise to the reader.

Re:Ctop – commandline monitoring for containers by dominotw on Thursday March 09, 2017 @04:31PM (#13833907)
even if protected by tls?
Re:Ctop – commandline monitoring for containers by zenlikethat on Thursday March 09, 2017 @07:00PM (#13835057)
Not sure why you're getting down-voted, exposing the Docker API over a TCP socket using TLS is the only way to even hope to do it safely.
Re:Ctop – commandline monitoring for containers by andrewguenther on Friday March 10, 2017 @02:53PM (#13841532)
Not exposing it over TCP at all is the only way to do it safely...