You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/running.md
+25Lines changed: 25 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -103,6 +103,31 @@ If you are using Docker with the LXC exec driver, then you need to manually spec
103
103
104
104
This is a problem seen in older versions of Docker. To fix, start cAdvisor without the `--volume=/:/rootfs:ro` mount. cAdvisor will degrade gracefully by dropping stats that depend on access to the machine root.
105
105
106
+
### Rootless (Docker / Podman)
107
+
108
+
Running cAdivsor on rootless container runtimes works for the most part. However granting access to the host kernel message buffer (`--device /dev/kmsg`) for OOM (out of memory) detection does not work.
109
+
110
+
Based on the container runtime used the socket needs to be changed appriopriately. Additionally the container storage volume, must be changed to the corresponding container runtime user directory. When using Podman you must also include `--volume=/sys/fs/cgroup:/sys/fs/cgroup:ro`.
111
+
112
+
```sh
113
+
VERSION=v0.49.1 # use the latest release version from https://github.com/google/cadvisor/releases
114
+
docker run \
115
+
--volume=/:/rootfs:ro \
116
+
--volume=/var/run:/var/run:ro \
117
+
--volume=/sys:/sys:ro \
118
+
# --volume=/sys/fs/cgroup:/sys/fs/cgroup:ro \ # Required for Podman subcontainers
cAdvisor is a static Go binary with no external dependencies. To run it standalone all you should need to do is run it! Note that some data sources may require root privileges. cAdvisor will gracefully degrade its features to those it can expose with the access given.
0 commit comments