Error running Netdata agent in Docker

Environment

Debian 11, Docker container

Problem/Question

NetData not working. Cannot run.
Getting Error in the log:

“ls: /var/run/balena.sock: No such file or directory
Netdata detected docker.sock
Account databases are not writable, assuming you know what you’re doing and continuing.
chown: unknown user/group netdata:root”

What I expected to happen

netdata to work.

Can you try again with the latest? It should be fixed in the latest nightly build.

Having the same issue.

OK, after the update to new version it started to boot, but the log gives me a different errors.

“ls: /var/run/balena.sock: No such file or directory
Netdata detected docker.sock
Creating docker group 998
addgroup: group ‘docker’ in use
Could not add group docker with ID 998, its already there probably
Assign netdata user to docker group 998
2021-09-10 07:51:34: netdata INFO : MAIN : CONFIG: cannot load cloud config ‘/var/lib/netdata/cloud.d/cloud.conf’. Running with internal defaults.
2021-09-10 07:51:34: netdata INFO : MAIN : Using host prefix directory ‘/host’
2021-09-10 07:51:34: netdata INFO : MAIN : TIMEZONE: using TZ variable ’ ‘Europe/Prague’’
2021-09-10 07:51:34: netdata INFO : MAIN : TIMEZONE: fixed as ‘Europe/Prague’
2021-09-10 07:51:34: netdata INFO : MAIN : SIGNAL: Enabling reaper
2021-09-10 07:51:34: netdata INFO : MAIN : process tracking enabled.
2021-09-10 07:51:34: netdata INFO : MAIN : resources control: allowed file descriptors: soft = 1048576, max = 1048576
2021-09-10 07:51:34: netdata INFO : MAIN : Adjusted my Out-Of-Memory (OOM) score from 0 to 1000.
2021-09-10 07:51:34: netdata ERROR : MAIN : Cannot adjust netdata scheduling policy to idle (5), with priority 0. Falling back to nice. (errno 38, Function not implemented)
2021-09-10 07:51:34: netdata ERROR : MAIN : Cannot get my current process scheduling policy. (errno 38, Function not implemented)
2021-09-10 07:51:34: netdata INFO : MAIN : netdata started on pid 1.
2021-09-10 07:51:34: netdata FATAL : MAIN : Cannot create directory ‘/var/lib/netdata/registry’. # : Invalid argument
2021-09-10 07:51:34: netdata INFO : MAIN : EXIT: netdata prepares to exit with code 1…
2021-09-10 07:51:34: netdata INFO : MAIN : EXIT: cleaning up the database…
2021-09-10 07:51:34: netdata INFO : MAIN : Cleaning up database [0 hosts(s)]…
2021-09-10 07:51:34: netdata INFO : MAIN : EXIT: all done - netdata is now exiting - bye bye…”

and it is not starting, so the issue stays, different reason.

Does this include having recreated the container or not? I’m not able to reproduce this same problem locally.

I tried recreate the container with my docker compose file, deleted the stack and re created it again, same outcome.

OK, I am closing this, i had to delete all Volumes and let Docker to recreate them and now it is working.

Greetings. By chance, I was trying to solve this same problem and after searching and researching and testing I found the cause. It turns out that this same behavior happens when we declare the VOLUMES in a directory that is not the one used by Docker by default and the CONTAINER does not have permissions to access those directories. An easy solution is to give 777 permissions to the necessary directories, as long as it doesn’t affect the security of the container. If you want to replicate this problem, just create the VOLUMES directories in /root, for example: volumes:
- /home/serveradmin/docker_volumes/netdata/netdataconfig:/etc/netdata
- /home/serveradmin/docker_volumes/netdata/netdatalib:/var/lib/netdata
- /home/serveradmin/docker_volumes/netdata/netdatacache:/var/cache/netdata