RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
See https://bugzilla.redhat.com/show_bug.cgi?id=1111916

(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:
http://perf1.perf.lab.eng.bos.redhat.com/jeder/docker/nsinit/nsinit-stats.out
http://perf1.perf.lab.eng.bos.redhat.com/jeder/docker/nsinit/nsinit-config.out

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
/usr/bin/nsinit
/usr/share/doc/golang-github-docker-libcontainer
/usr/share/doc/golang-github-docker-libcontainer/LICENSE

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:

https://bugzilla.redhat.com/show_bug.cgi?id=1130500

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).

Thoughts?

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