-
Notifications
You must be signed in to change notification settings - Fork 527
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
Shows docker containers but no usage on OVH Dedicated #24
Comments
Thanks for the details; can you provide the output of |
|
Most likely you're on a very outdated server. I think about 1.11 (you're at 1.6) adds monitoring capabilities, somewhere around api 1.21-1.23. Also the kernel version is quite outdated, so most likely you're in for an upgrade, before you can use ctop. Edit: keep in mind that docker somewhere from 1.10-12 also switched to a newer registry (v2). With your installation I don't even think you can pull new images from docker hub/etc. It's very old. |
Damn. Default debian packaging. Thanks! You might add in your readme that you need docker v1.21 ? |
I believe the minimum version requirement is 1.8; however, I'll need to do some changelog review to be sure. |
According to the official docs at least, 1.18 API should already have the stats endpoint https://docs.docker.com/engine/api/v1.18/ Most likely just the response contents are different and ctop runs into a load/parse error. I'm completely guessing here. |
Hi,
I have a dedicated server at OVH, and the current release of CTOP seems to not work on it:
I can see my one container, but there's no mem/cpu/rx-tx working it seems, even though I'm using the container and top sees activity.
Uname -a:
Processor is (there's 4 of them):
ctop version is:
If you need extra info, ask away.
Also, I didn't try compiling on premises, I used the release.
The text was updated successfully, but these errors were encountered: