Jump to content

KyleK29

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by KyleK29

  1. 3 hours ago, sfef said:

    I can not get the exclusions to work. Reading through these posts I am pretty confident that I should set it to /docker-sys/.*

    I have tried variations on that and also including the cache drive name /nvme_1_nvme/ 

    When I first installed zfs master I had a parent folder above my docker-sys folder. It was /docker/docker-sys/ when this was my folder scheme I remember them being excluded. However I have now removed that parent folder and the docker-sys folder is its own dataset.

    I have dozens of these docker images listed.

     

    image.png.342e9dd4a9ffff2bf38fff71a5e225a2.png

     

    I had to tinker with mine to get it to work as well.

     

    My setup, Docker-Directory is set to: 

    /mnt/zfspool/.docker_system/docker_directory/

     

    ZFS Master Exclusion is set to:

    .docker_system

     

     

     

  2. Alright, got it working again with a forked image. If anyone else wants to try (I do recommend spinning up a different copy, just for testing purposes). All you have to do is swap the repository of the GUS package / Docker container to this (right-click the Docker Containers Icon --> Edit --> find "repository"): 
     

    kylek29/grafana-unraid-stack-2023:latest

     

    That is a new forked image, which adds additional layers to the grafana-unraid-stack image by testdasi. Changes made:

     

    • Add a new install script that will install the new apt-key certs from Grafana/Influxdb, then reinstall latest InfluxDb/Telegraf, and perform clean up.
    • Added tweaks to the healthcheck command so that it fires every 30seconds and will wait 30seconds for the machine to start (I noticed it often failed with the original images 0s parameters).
    • Fixed a bug where the healthcheck status would fail and not detect the Grafana Server pid. It will now display the proper statuses of starting, healthy, and unhealthy.
    • Fixed an issue where Tini (init handler) was failing.

     

     

    To look at the code and Dockerfile, see here: https://github.com/kylek29/misc_code/tree/main/unRAID/Grafana-Unraid-Stack

     

    For general usage, see the original post. This is just a fix layer.

    • Like 3
    • Thanks 3
    • Upvote 1
  3. For those installing this through the unRaid app tab, you may encounter the dashboards being blank and the Docker Logs saying something about the Influxdb.exe not being installed.

     

    As another user mentioned, the problem is in the influx setup.

     

    How I Fixed It:

    1. Launch a Docker Terminal (in unRAID, click the docker's icon -> Console )
    2. Verify issue, type cmd: 
      1. /static-ubuntu/grafana-unraid-stack/healthcheck.sh
      2. You should see "Executable /usr/bin/influxd does not exist!"  -- if you do, proceed.
    3. Go to /data directory -->
      cd /data

       

    4. Download the corrected install script ( https://raw.githubusercontent.com/kylek29/misc_code/main/unRAID/Grafana-Unraid-Stack/fix_influxdb_2023.sh ) with this command: 
      curl -sOL https://raw.githubusercontent.com/kylek29/misc_code/main/unRAID/Grafana-Unraid-Stack/fix_influxdb_2023.sh

       

    5. Give it execution permissions:
      chmod +x fix_influxdb_2023.sh
    6. Execute the script. 
      ./fix_influxdb_2023.sh

       

    7. Verify error is gone.
      /static-ubuntu/grafana-unraid-stack/healthcheck.sh

       

     

    Now go to the admin dashboard and verify it's receiving data. If you go to the your datasources section -> influxdb -> bottom, "test" button --> it should say "datasource is working" now.

     

     

    *EDIT* That didn't last long. I decided to do a completely fresh install to test the above instructions one more time (complete with purged image, etc.), this time it didn't work. Data doesn't come through. Using the old image tag mentioned earlier does seem to work: testdasi/grafana-unraid-stack:s230122


    If I figure out the missing step I did when I got it completely working with the :latest image, I'll update this post.

     

     

  4. On 3/2/2023 at 9:12 AM, samsausages said:

    Yeah, I read that and it seems silly to run a VM for what is usually a highly dependent core feature.  Reverse proxies work very well, but I don't see how they replace proper user & group permissions as a security layer, when using web facing docker containers.

    I like Unraid for the storage array, everything else has been a nice bonus.  If I spool up a VM, I'd probably Virtualize Unraid and use it just for the storage array, then run VM's and Docker on the host.
    But that makes everything a bit overly complicated for my liking.

     

    Just came here to say this. I hope they consider adding it for unRAID 7 (or whatever next major version is). I've always used groups to configure separation of concerns for users, even in a home environment. The current vanilla way of doing it is way too lax for my liking and having to abstract to a VM just to handle file sharing on the native OS seems like an unnecessary hurdle.

    • Like 1
×
×
  • Create New...