Description of problem:
(In reply to Vincent Batts from comment #1)
> and github.com/codegangsta/cli when we decide to start building `nsinit`
Look at all this glorious data:
I'd imagine any customer looking for per-container statistics would strongly prefer a utility rather than spelunking through /sys/fs/cgroups and /sys/class/net to glue it all together.
In the end it would be nicer to have 'docker stats/config <CONTAINER_ID>', but in lieu of that, is any reason we're not building and shipping nsinit ?
The build/inclusion of nsinit in Fedora is complete via BZ1111916, and nsinit is in
$ rpm -ql golang-github-docker-libcontainer
But, 'nsinit stats' actually doesn't work on Fedora at the moment because it can't find the memory cgroup due to the way we've wired up systemd. A very old version of nsinit was built for Fedora, and I'm not sure why. Head of libcontainer git nsinit works fine on RHEL7.
I thought for RHEL7, nsinit should be included in the docker RPM itself...
Just want to make sure we pick up the latest for RHEL7:
There was an issue filed on github to include nsinit in the main docker repo itself, though I can't seem to find it atm. Dan, Vincent do you happen to know what was the outcome of that?
hmm here it is: https://github.com/docker/docker/pull/7248 ... Closed atm.
RHEL7 would need the golang-github-docker-libcontainer package included (since it's technically a separate repo now) unless we choose to build and install libcontainer and nsinit from within the vendor dir in docker (which would be way more convenient). The latter approach might be trouble in case docker and libcontainer updates are not in sync (but I could be wrong here).
I would say we ship them together. Hopefully eventually docker stats or some such call gets developed, but for now I think we should ship them together.
Fixed in docker-1.2