netdata not showing container names

Currently reading
netdata not showing container names

245
47
NAS
DS918+, DS414j
Operating system
  1. Linux
  2. Windows
  3. other
Mobile operating system
  1. Android
Hi,
I'm looking at real time monitoring with netdata.
Looking at the network interfaces I get docker0<code> rather than the name of the container.
1611564602375.png

Is there any way to get it to provide the container's name? If not how would I look trace it back to a container?

My docker compose:
version: '3'
services:
netdata:
image: netdata/netdata
container_name: netdata
ports:
- 19999:19999
restart: unless-stopped
cap_add:
- SYS_PTRACE
security_opt:
- apparmor:unconfined
volumes:
- /volume2/docker/netdata/config:/etc/netdata
- /volume2/docker/netdata/lib:/var/lib/netdata
- /volume2/docker/netdata/cache:/var/cache/netdata
- /etc/group:/host/etc/group:ro
- /proc:/host/proc:ro
- /sys:/host/sys:ro
- /var/run/docker.sock:/var/run/docker.sock:ro
Any help greatly appreciated.
 
Be sure to read docker container names resolution in NetData docs. It explains how you can make this work. Considering that netdata is a contianer as well, it doesnt have permissions to read that kind of info (even though it is already configured to translate names automatically).

So to make this work you will need to do any of the methods described in the document.

Quick and unsafe way is to run your docker container with 2 variables: -e DOCKER_GRP=root and -e DOCKER_USR=root. This way you are allowing netdata container root permission on your host, so be sure that you want to do that.

End result is as expected:
Screenshot 2021-01-25 at 11.16.40.png
 
So, I ran:

As per the instructions and got:
65537
So added:

But I'm still getting the same as the above screen grab.. :(
Well, you have 2 more methods to try out. Also be sure that if you have added this variable, that you also still have docker.sock volume bind. Not sure how you added this variable, but unless you used docker run or compose it might have not applied.
 
Added in the docker compose.
Not keen on running as root, for obvious reasons.
I'm just unsure as to why this works with other containers and not this one.
Guess I'll have to look into a socket-proxy
Thanks for your help with this @Rusty
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

Sorry, I read your post late. You already did it. Thanks,
Replies
3
Views
943
I can’t find any option to restore just the settings. 1710356648 Phew, managed to fix it. Within the...
Replies
4
Views
580
  • Question
Open an issue on that GitHub page. The developers will be glad to assist. OP has posted two threads on...
Replies
5
Views
1,232
I'm happy with email notifications but in v0.3.3 of dockcheck the author added apprise notifications...
Replies
4
Views
1,445
Hi, I'll start by saying, my understanding of networking is very limited so I apologize if I'm asking an...
Replies
0
Views
844
You can run cmd.exe to get a command window from which you can execute SSH commands. However, my personal...
Replies
36
Views
3,826
I can confirm it's not in the list. All I've got are the following: Worth noting that I'm already...
Replies
4
Views
1,324

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Back
Top