• Content Count

  • Joined

  • Last visited

Community Reputation

11 Good

About roland

  • Rank


  • Gender
  • Location
    Sydney Australia

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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 the
  2. 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.
  3. 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: thanks for all your help.
  4. Check out the how to change the configuration topic in the first post.
  5. Hi @dbinott, I don't know, as I don't have NVIDIA in my system. Maybe @Dazog can enlighten us...
  6. You are correct, I will change that to make it more generic
  7. 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: 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 w
  8. Turns out the reboot did not work either. Had to turn the box off! Now everything is back up and running. Thanks, @Squid for looking into it!
  9. Yep, the new one is
  10. Thanks for the super quick response, I have an idea what docker that might have been and I believe it is disabled now. But, I have rebooted, and unfortunately am still back at the 504. The dockers don't start either. Any further ideas on what can get me back up running???
  11. Hi, my tower was working for years without any problems. Today it all went bad. The guy is stuck at 504 Gateway Time-out and I don't know where to start looking for the problem. I usually have a bunch of dockers running. Plex, HomeAssistant, LetsEncrypt, MQTT, ... But they are all down now. diagnostics attached Any hint on where to start digging would be great! Thanks
  12. Hi @drdebian I haven't tried it, but there are instructions on the docker hub Page on setting up emails
  13. 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?
  14. Yes, the docker got updated a lot lately. 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)
  15. I accepted a merge request 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: