dw

+1 this would be great. would make it much easier see new log events while debugging

Hi, did you have any luck with this? I get the same on both ubuntu an CoreOS docker version 1.4.1 my docker run command is ``` docker run -p 9104:9104...

Hi discordianfish, thanks for the update. Unfortunately it did not fix the issue. most container_\* metrics still show as 0. you can see results here http://104.236.149.72:9104/metrics I made sure to...

I also run into a issue when trying to build. ``` Step 6 : RUN go get -u -d && go build ---> Running in 23d3ed1ed0f5 package github.com/docker-infra/container-exporter: github.com/docker-infra/container-exporter is...

build issue caused by incorrect paths in docker and cadvisor I have create issues in both repos here https://github.com/docker/docker/issues/10976 https://github.com/google/cadvisor/issues/533

still the same for me on CoreOS, ~~have not tested Ubuntu yet.~~ The same on Ubuntu, all container stats are 0 will check cgroup path later today

on CoreOS path is like this ``` /sys/fs/cgroup/cpuacct/system.slice/docker-094c63915d3d594727ecc4061b55451784141c8f7101ad1db5f6e3c29c121c3a.scope/cpuacct.usage ``` I can get results from both host or container ``` cat /sys/fs/cgroup/cpuacct/system.slice/docker-094c63915d3d594727ecc4061b55451784141c8f7101ad1db5f6e3c29c121c3a.scope/cpuacct.usage 242753876 docker exec evil_poitras cat /cgroup/cpuacct/system.slice/docker-094c63915d3d594727ecc4061b55451784141c8f7101ad1db5f6e3c29c121c3a.scope/cpuacct.usage 241811678 ```