roland

This post discusses the opposite problem but it suggests we should be able to map the cache directory to persist the data. https://community.netdata.cloud/t/clear-historical-data-from-netdata-docker-container/818 The netdata docker has come a long way since I created this template. Maybe it is time to review the configuration completely. But currently I don't have the time to dig deeper into this. Happy to accept pull requests if someone has a better version.

can you please check this and see if that solves it?

fixed now, at least I was consistent

it worked for me. log on to your unRAID. keep a copy of your config file. stop your netdata container assuming /mnt/cache/appdata/netdata/ is the folder where you store the config. cd /mnt/cache/appdata/netdata/ mkdir netdataconfig docker run -d --name netdata_tmp netdata/netdata docker cp netdata_tmp:/etc/netdata netdataconfig/ docker rm -f netdata_tmp copy the config file you want to use to /mnt/cache/appdata/netdata/netdataconfig/netdata in the docker configuration change the volume that maps the config file to map to the new config directory restart the container and it should be there. I only checked the change of the hostname, but that worked fine.

There seems to be a different way to do this now. I have not had the chance to try that yet, but see here: https://learn.netdata.cloud/docs/agent/packaging/docker/#host-editable-configuration

I am not using this plugin, but have you seen this explanation? https://github.com/netdata/netdata/issues/6681

Just updated to the latest release and it is working ...

OK, I missed it. The official docker does not support the override folder that the previous version had. So if we need config files, we need to mount them one-by-one. To start with the master config file, get the template from your netdata docker: wget [your_netdata_ip]:19999/netdata.conf then edit that file and mount it into the docker: -v '/mnt/cache/appdata/netdata/netadata.conf':'/etc/netdata/netadata.conf':'rw' 'ro' might be good enough you can repeat that with all other files that you need. Sorry, this seems to be the only solution they support currently. I will remove the override mount from the template now.

This is the default behaviour in the vanilla netdata installation. I don't believe it is my place to disable it for everyone by default, but this makes it easy and in my opinion obvious to everyone that uses this template to at least think about it. https://docs.netdata.cloud/docs/anonymous-statistics/#opt-out

Thank you all! @L0rdRaiden @Squid @Dazog I have - updated the template to point to the official docker - added the PGID as well as the DO_NOT_TRACK variable - updated the logo again. the template is on github: https://raw.githubusercontent.com/Data-Monkey/docker-templates/master/Data-Monkey/netdata.xml thanks for all your help.

Check out the how to change the configuration topic in the first post.

Hi @dbinott, I don't know, as I don't have NVIDIA in my system. Maybe @Dazog can enlighten us...

You are correct, I will change that to make it more generic

Hi, sorry for the long absence. I think you should be able to add the file into the override folder and it should persist. I don't have a nvidia and can't test it. See this section: Adding custom alarms, charts and configuration overrides on the dockerhub description: https://hub.docker.com/r/titpetric/netdata Please let me know if you think something else is required. I don't maintain the docker container, just made the template for easy use in unRAID. Edit: @Dazog @dbinott I think the change a while back where the override folder was created did not work properly anymore with my template. Please change the docker mapping from: -v '/mnt/cache/appdata/netdata':'/etc/netdata':'rw' to this and try if this works: -v '/mnt/cache/appdata/netdata':'/etc/netdata/override':'rw' it works for me for the normal netdata.conf file. If you could confirm this works I will change the template to make it easier for the next users. Edit2: turns out I made that change in the template more than a year ago ... just never changed my own setup. SO if you added netdata recently it should work! regards Roland

Hi @drdebian I haven't tried it, but there are instructions on the docker hub Page on setting up emails https://hub.docker.com/r/titpetric/netdata

Hi, maybe a bit off-topic, but I hope you guys have a good opinion on this. I am trying to "backup and document" my setup on Github. Will the complete nginx reverse proxy config potentially reveal too much detail to share? subdomains/ports/forwards/ ..... Of course, I won't post the .htaccess file, but I wanted all other files there. *.conf and all site-confs/* What do you think?

Yes, the docker got updated a lot lately. https://hub.docker.com/r/titpetric/netdata/builds/ This template just follows the docker build. And I think that build follows the commits on netdata. But do you really need to have the most up to date version all the time? Just set it to auto update once a day and forget about it.... (At least this is my approach)

I accepted a merge request https://github.com/Data-Monkey/docker-templates/pull/3 to change the default config mapping to /etc/ netdata /override From the merge request, thanks a lot acrelle: Change the default netdata configuration to be /etc/netdata/override. Scripts placed in here are automatically copied into /etc/netdata during the container start script. /etc/netdata/override is the volume exposed in the original Dockerfile: https://hub.docker.com/r/titpetric/netdata/~/dockerfile/

I have recreated everything again and it works now.... thanks for all your hard work @binhex ! a beer is on its way!

Hi @L0rdRaiden, Sorry, I have been missing for a while. THere has been some development to the docker by titpetric over at dockerhub. From his page: https://hub.docker.com/r/titpetric/netdata/ Adding custom alarms, charts and configuration overrides To add custom alarms, charts or to override any default configuration file, mount a volume to the container to /etc/netdata/override, like -v /opt/netdata/overrides:/etc/netdata/override. Then, place your config files in the directory as if it was /etc/netdata/. For example to create a custom alarm for system temperature, create a health.d folder in your local directory (/opt/netdata/override in the example above) and place a sensors.conf file with your alarm configuration inside the health.d directory. By default my template maps /etc/netdata to your config directory, in my case /mnt/cache/appdata/netdata inside there you should find the override folder. Most likely empty. But that is where you can add your configurations. I have not tried this yet, the things you mention show up in my config by default.

Done ! Thanks @realies for pointing out the obvious. GitHub is updated. https://github.com/Data-Monkey/docker-templates/blob/master/Data-Monkey/netdata.xml

Hi binhex, yes it looks like the example you showed. I am using the linuxserver.io version and there is one more option to ADD PAUSED but other than that it is the same. I also tried all different toggle options and confirmed the password. But no joy. In the deluge preferences, the WebUI plugin is not ticked, but the web login works fine. Should it be ticked? (Sorry, at work now, can't get a screenshot) edit: I also just upgraded to the latest unRAID OS version, maybe that did it? (Too many changes to my system in one go without proper testing in between....) Thanks Roland

Hi, I have been running an old version of this docker for a long long time and it worked perfectly. I was stuck on the old version due to some VPN issues but they are resolved now and the current version works fine with my VPN. Thanks for that!! But here is my new problem, my sonarr does not talk to deluge anymore. The error I get is this: Unknown exception: The request timed out: 'http://192.168.2.130:8112/json' Deluge is configured on the default port and password. Looking for answers: https://forums.sonarr.tv/t/solved-linking-sonarr-to-deluge/13364/3 This suggests to enable the WebUI plugin in Deluge, but I can't enable it. The Apply or OK button don't work and it always returns to disabled. I have a feeling I encountered this before, but I can't figure it out this time. What kind of addtional details would you need? I am fairly sure it is something simple that I am missing! btw CP is still working, but I think they use different protocols. Thanks

The official netdata docker has a github commit hook, so that whenever there is a new commit to it, it's building a new docker image. And as far as you can see in the GitHub commit log, there are daily commits. You can install the auto update plugin (CA Auto Update Applications ) and just keep up-to-date that way.

Hi @binhex my VPN provider released an updated certificate and I just tried to update it here. The openvpn protocol is TCP-CLIENT But when I define this in the VPN_PROTOCOL variable the iptables command does not like it. iptables v1.6.1: unknown protocol "tcp-client" specified When I change it to TCP the openvpn command complains: [debug] OpenVPN command line '/usr/bin/openvpn --cd /config/openvpn --config /config/openvpn/swissvpn.ovpn --daemon --dev tun0 --remote connect.swissvpn.net 1194 --proto tcp --reneg-sec 0 --mute-replay-warnings --auth-nocache --keepalive 10 60 --setenv VPN_PROV custom --script-security 2 --up /root/openvpnup.sh --up-delay --up-restart --auth-user-pass credentials.conf --log-append /config/supervisord.log' Options error: --proto tcp is ambiguous in this context. Please specify --proto tcp-server or --proto tcp-client 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.4 I have now hardcoded the tcp-client value in your openvpn.sh script and defined VPN_PROTOCOL = tcp and that works. The same variable needs to have two different values at different points in the scripts. # define common command lne parameters for openvpn openvpn_cli="/usr/bin/openvpn --cd /config/openvpn --config ${VPN_CONFIG} --daemon --dev ${VPN_DEVICE_TYPE}0 --remote ${VPN_REMOTE} ${VPN_PORT} --proto tcp-client --reneg-sec 0 --mute-replay-warnings --auth-nocache --keepalive 10 60 --setenv VPN_PROV ${VPN_PROV} --script-security 2 --up /root/openvpnup.sh --up-delay --up-restart" But obviously that is not a permanent solution. Any chance you could look into this sometime? EDIT: if it helps, the provider is SWISSVPN.net