What about showing stats for all running containers if <containers...> is not specified? You can run docker stats $(docker ps -q), but showing stats for everything that is running looks like a sane default.

can you go up the exact number of lines and rewrite on top of it, instead of clearing the screen.

(that's how we do for pull)

@bobrik I guess it would depend on how many containers you have. You can always do

docker stats `docker ps -q`

exited containers aren't handled properly

@vieux I think exited containers should get zeroed out then when they start again you start getting metrics. What do you think of that functionality ?

@crosbymichael I mean the cli is hanging and waiting for

I got a panic when trying to delete a container:

DEBU[0010] Calling DELETE /containers/{name:.*}
INFO[0010] DELETE /v1.16/containers/b0808d936b19?force=1
INFO[0010] +job rm(b0808d936b19)
INFO[0010] -job rm(b0808d936b19)
2015/01/08 23:28:30 http: panic serving @: runtime error: invalid memory address or nil pointer dereference
goroutine 42 [running]:
net/http.func·011()
    /usr/local/go/src/net/http/server.go:1130 +0xbb
github.com/docker/docker/daemon.(*statsCollector).stopCollection(0xc20822b780, 0xc208035ba0)
    /go/src/github.com/docker/docker/daemon/stats_collector.go:66 +0x141
github.com/docker/docker/daemon.(*Daemon).ContainerRm(0xc2080dbad0, 0xc208031100, 0x2)
    /go/src/github.com/docker/docker/daemon/delete.go:54 +0x7a2
github.com/docker/docker/daemon.*Daemon.ContainerRm·fm(0xc208031100, 0x7ffbfc292270)
    /go/src/github.com/docker/docker/daemon/daemon.go:118 +0x31
github.com/docker/docker/engine.(*Job).Run(0xc208031100, 0x0, 0x0)
    /go/src/github.com/docker/docker/engine/job.go:83 +0x936
github.com/docker/docker/api/server.deleteContainers(0xc2080db4a0, 0xc2081e9f89, 0x4, 0x7ffbfc29a990, 0xc2082030e0, 0xc208033e10, 0xc208144570, 0x0, 0x0)
    /go/src/github.com/docker/docker/api/server/server.go:768 +0x39e
github.com/docker/docker/api/server.func·002(0x7ffbfc29a990, 0xc2082030e0, 0xc208033e10)
    /go/src/github.com/docker/docker/api/server/server.go:1243 +0x940
net/http.HandlerFunc.ServeHTTP(0xc2080563c0, 0x7ffbfc29a990, 0xc2082030e0, 0xc208033e10)
    /usr/local/go/src/net/http/server.go:1265 +0x41
github.com/gorilla/mux.(*Router).ServeHTTP(0xc208095220, 0x7ffbfc29a990, 0xc2082030e0, 0xc208033e10)
    /go/src/github.com/docker/docker/vendor/src/github.com/gorilla/mux/mux.go:98 +0x2b9
net/http.serverHandler.ServeHTTP(0xc208054fc0, 0x7ffbfc29a990, 0xc2082030e0, 0xc208033e10)
    /usr/local/go/src/net/http/server.go:1703 +0x19a
net/http.(*conn).serve(0xc208202e60)
    /usr/local/go/src/net/http/server.go:1204 +0xb57
created by net/http.(*Server).Serve
    /usr/local/go/src/net/http/server.go:1751 +0x35e

Fixed the panic

@vieux fixed the issue where you request stats for a non running container, it will go ahead and add it then when it's started you see the stats start flowing in.

@crosbymichael It's like what @LK4D4 said. We may want to get the one-time status of containers.

I noticed if I run
$ docker stats $(docker ps -q) and in second console start new container above view will not be automatically refreshed to include container(s) started after
$ docker stats $(docker ps -q) was started
tested with binaries attached earlier by @jfrazelle

@ekuric This is expected $(docker ps -q) is only run once, and is only pulling those ids.

@cpuguy83 ah,yes, thank you,sorry for noise

Thanks! This is a great addition. Are there plans to let users control the frequency with which they can extract stats data from the api endpoint? 1 second may be too aggressive when there are a lot of containers running on a host.

The CPU usage % seem to be stuck at 0% for me. Being able to monitor the growing size of a running container and its disk I/O would also be very useful.

Thanks for this new feature. Works like a charm

@usertaken if you want disk IO for monitoring hit the API, the CLI is very dumbed down for a quick and simple view. If you are using this for monitoring use the api

very nice stuff!

I'm also waiting for the option like --count or something that just capture the stats once. It will be very useful when getting remote parameter.

+1 to the count option. I'd love to create a New Relic plugin for this data but there is a lot of extra work I have to do if I don't have control over the polling interval (plus the consumption of a continuous stream is much more involved process)

For me, I would like to get the current stats of the containers and no need to return the whole stream. It would be great to support this feature 😃

I agree :)

+1 for a simply way of just getting current stats as opposed to subscribing and disconnecting

@SvenDowideit API docs need a bit more info on what the cpu numbers mean and how you go about converting them to % cpu

+1 for just getting current numbers without subscription. @crosbymichael I can create a separate issue.

+1 :)

👍

Stats are nice. Thanks.

Here's a one-liner that does what you would expect docker stats to do:

docker stats `docker ps | tail -n+2 | awk '{ print $NF }'`

However, the flicker is distinctly unpleasant.

I love and appreciate the concept and current possibilities, however I have some thoughts:

I don't understand why it is repeating (or why it doesn't have the count flag). I could eg. use 'watch' and its features to show me a constant update if I want that.

I also find it hard to imagine writing a simple script to parse the json data if it has to be running forever. I'd rather query once a minute and send those stats to graphite (just an example), but I don't see how I could accomplish this in a simple way (someone has any thoughts?)

I would also appreciate the presence of an 'all' option, especially for the json-part (where you would have to run several queries to get all container data)

+1 for a count option.

Please stop adding new feature requests to a closed/merged PR. If you have an enhancement/feature request, open a new issue.

For those looking for a "count" option; there is a PR that implements a --no-stream flag, which will return the stats only once; Allow pulling stats once and disconnecting. #10766