Skip to content
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

Closed
Gui13 opened this issue Mar 10, 2017 · 6 comments
Closed

Shows docker containers but no usage on OVH Dedicated #24

Gui13 opened this issue Mar 10, 2017 · 6 comments

Comments

@Gui13
Copy link

Gui13 commented Mar 10, 2017

Hi,

I have a dedicated server at OVH, and the current release of CTOP seems to not work on it:

capture d ecran 2017-03-10 a 07 51 12

capture d ecran 2017-03-10 a 07 54 46

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:

Linux xxxx 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-2+deb8u3 (2016-07-02) x86_64 GNU/Linux

Processor is (there's 4 of them):

cat /proc/cpuinfo
processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 54
model name	: Intel(R) Atom(TM) CPU N2800   @ 1.86GHz
stepping	: 1
microcode	: 0x10d
cpu MHz		: 798.000
cache size	: 512 KB
physical id	: 0
siblings	: 4
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl nonstop_tsc aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm movbe lahf_lm arat dtherm
bogomips	: 3733.22
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

ctop version is:

wget https://github.com/bcicen/ctop/releases/download/v0.4/ctop-0.4-linux-amd64 -O ctop

If you need extra info, ask away.

Also, I didn't try compiling on premises, I used the release.

@bcicen
Copy link
Owner

bcicen commented Mar 10, 2017

Thanks for the details; can you provide the output of docker version on the host server?

@Gui13
Copy link
Author

Gui13 commented Mar 10, 2017

$ docker version
Client version: 1.6.2
Client API version: 1.18
Go version (client): go1.3.3
Git commit (client): 7c8fca2
OS/Arch (client): linux/amd64
Server version: 1.6.2
Server API version: 1.18
Go version (server): go1.3.3
Git commit (server): 7c8fca2
OS/Arch (server): linux/amd64

@titpetric
Copy link

titpetric commented Mar 10, 2017

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.

@Gui13
Copy link
Author

Gui13 commented Mar 10, 2017

Damn. Default debian packaging. Thanks! You might add in your readme that you need docker v1.21 ?

@Gui13 Gui13 closed this as completed Mar 10, 2017
@bcicen
Copy link
Owner

bcicen commented Mar 10, 2017

I believe the minimum version requirement is 1.8; however, I'll need to do some changelog review to be sure.

@titpetric
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants