-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cadvisor cannot start #89
Comments
I made changes in my docker-compose.yml: 146.222.75.203 is the host IP I deploy the prometheus.
|
@siuwwong5 change 146.222.75.203 to "hostname" |
@llitfkitfk change 146.222.75.203 to the hostname, right? |
@llitfkitfk Thanks a lot! it is working now [root@hln2184p prometheus-version-2]# docker ps |
@llitfkitfk Sorry, the cadvisor cannot start, and seems it keeps restart. |
@siuwwong5 Can I see the log? |
[root@hln2184p prometheus-version-2]# docker logs --follow ca3cb8ab191d |
[root@hln2184p prometheus-version-2]# ls -al /sys/fs/cgroup/cpu* /sys/fs/cgroup/cpu,cpuacct: /sys/fs/cgroup/cpuset: |
Thanks a lot. The fix can help. [root@hln2184p prometheus-version-2]# mount -o remount,rw '/sys/fs/cgroup' |
Provide a general summary of the issue in the Title above
If you're describing a bug, tell us what should happen
If you're suggesting a change/improvement, tell us how it should work
Expected Behaviour
Current Behaviour
cadvisor docker container cannot start
logs:
I1227 06:57:44.608799 1 manager.go:1178] Started watching for new ooms in manager
W1227 06:57:44.608845 1 manager.go:313] Could not configure a source for OOM detection, disabling OOM events: open /dev/kmsg: no such file or directory
I1227 06:57:44.611828 1 manager.go:329] Starting recovery of all containers
I1227 06:57:44.709836 1 manager.go:334] Recovery completed
F1227 06:57:44.711196 1 cadvisor.go:156] Failed to start container manager: inotify_add_watch /sys/fs/cgroup/cpuacct,cpu: no such file or directory
Possible Solution
Steps to Reproduce (for bugs)
Provide a link to a live example, or steps to reproduce this bug. Include code to reproduce, if relevant:
Your Environment
Include as many relevant details about the environment you experienced the bug in
Docker version
docker version
(e.g. Docker 17.0.05 ):docker 1.13.1
Operating System and version (e.g. Linux, Windows, MacOS):
linux
The text was updated successfully, but these errors were encountered: