-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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 docker container fails to start "mountpoint for cpu not found" (clearcontainers) #1943
Comments
The volumes look correct... I bet it is related to this limitation. You are trying to mount in |
I am getting this same error message. here is the relevant portion of my docker-compose
Here is the error I get:
any ideas? |
Try replacing image by |
I had same issue, and this solved! |
"mountpoint for cpu not found" google/cadvisor#1943
``` gcr.io/google-containers/cadvisor:latest ``` Mentioned image causes following issue when tried to run, please do visit the issue page of google cadvisor to know more about the issue. [cadvisor docker container fails to start "mountpoint for cpu not found" ](google/cadvisor#1943) Solution mentioned here was to use, ``` gcr.io/cadvisor/cadvisor ```
This helped solve mine too. Thanks |
I had problem with pulling image from |
After changing to
|
FIX: Use a version tag like gcr.io/cadvisor/cadvisor:v0.46.0 |
oh,gcr.io/cadvisor/cadvisor maybe can solve the problem,but i can't pull this image in china,has anyone as same as me?error message: |
For more details why have here a look: google/cadvisor#1943
This issue is fixed and needs to be closed, isn't it? |
En efecto esto soluciono mi problema |
it solve my probleme !!! |
This helped me. |
Thank you, this solved my problem |
It worked for me! on prod, on ubuntu, EC2 AWS. |
Thanks for tips, yes, agree this should be closed |
This helped. Thank you. |
this helps me to solve this problem. Thanks |
I am attempting to run cadvisor on Debian Stretch (without systemd). My docker setup is using clearcontainers and a backend with block-based sparse LVM storage (layered onto ZFS). Everything is functioning well with a broad range of containers.
When I try to start cadvisor, it gives the following log output:
I think this may be to do with some difficulties in accessing the volume for
/sys
, perhaps it is not permitted to be shared in this way...My
docker-compose.yml
is as follows:The text was updated successfully, but these errors were encountered: