From b582977bc8a7937a12b9064aa7fbe688b7d9c8fe Mon Sep 17 00:00:00 2001 From: Tom Barlow Date: Thu, 27 Aug 2015 10:39:37 +0100 Subject: [PATCH] Updated to use correct cgroup paths Signed-off-by: Tom Barlow --- docs/articles/runmetrics.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/articles/runmetrics.md b/docs/articles/runmetrics.md index 27bd4027e3..13fa77b177 100644 --- a/docs/articles/runmetrics.md +++ b/docs/articles/runmetrics.md @@ -78,7 +78,7 @@ in `docker ps`, its long ID might be something like look it up with `docker inspect` or `docker ps --no-trunc`. Putting everything together to look at the memory metrics for a Docker -container, take a look at `/sys/fs/cgroup/memory/lxc//`. +container, take a look at `/sys/fs/cgroup/memory/docker//`. ## Metrics from cgroups: memory, CPU, block I/O @@ -396,7 +396,7 @@ control group (i.e., in the container). Pick any one of them. Putting everything together, if the "short ID" of a container is held in the environment variable `$CID`, then you can do this: - $ TASKS=/sys/fs/cgroup/devices/$CID*/tasks + $ TASKS=/sys/fs/cgroup/devices/docker/$CID*/tasks $ PID=$(head -n 1 $TASKS) $ mkdir -p /var/run/netns $ ln -sf /proc/$PID/ns/net /var/run/netns/$CID