Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

21 Good

About primeval_god

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

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

  1. Unfortunately you may be on your own for this one. To my knowledge very few people use unRAID with Active Directory. I would assume even fewer if any try to do so within a docker container. The only thing I can help with is to point out that Community Applications has a mode where you can search docker hub for images that are not in the CA list. From there you will presented with a (mostly blank) template to fill out for the docker image. Then its just a matter of adding whatever run parameters that the image requires (usually specified by the image author on the docker hub page) to the corresponding areas of the Dockerman template.
  2. This. Best practice is to give docker containers access to only the things that they need. For instance my plex container has a read/write mount for its config /mnt/user/appdata/plex and read only mounts for my media shares /mnt/user/tv/ and /mnt/user/movies/
  3. @leonardwulf These two articles have some more in depth infor on it https://www.tomshardware.com/reviews/amd-ryzen-5-1600x-cpu-review,5014-2.html, https://www.anandtech.com/show/14525/amd-zen-2-microarchitecture-analysis-ryzen-3000-and-epyc-rome/11. The short of it though is that in the first 2 generations of Ryzen, the infinity fabric, which is the internal interconnect between Ryzen's core complexes, memory and peripherals, is clocked 1:1 with the RAM. Thus the speed at which your RAM runs directly determines the speed at which data can be moved around within the Ryzen processor.
  4. @Ambrotos I suspect the reason is a (not as widely known as it should be) difference in the way volumes and bind mounts work in docker. When a docker volume is created for a non-empty directory in a container, the volume is populated with the files in the containers directory. On the other hand if a host folder is bind-mounted to a non-empty directory in a docker container the bind-mounted folder replaces the container folder completely. Here is a link to the docker documentation explaining in more detail. Since unRAID users are encouraged to use bind mounts to the appdata folder rather than volumes this issue occasionally crops up. Especially for docker containers that were build with microservice or cluster usage in mind since those applications most often stay away from bind mounting to make containers services more portable between host nodes.
  5. Unfortunately that is not the way this plugin works. It does not include functionality for automatically waking your server. The time you added simply prevent it from going to sleep during those times if it is already on. To get wakeup to work you will need to insert a custom script to set an RTC wake alarm. There are various examples around the forums and farther back in this thread. The most recent I commented on is here Be warned though, RTC hardware support is notoriously inconsistent. Your system may or may not be capable of RTC wake. Take a look at the settings for the plugin with Help on. There is a way to save a log to determine why your server didnt sleep. I would take a shot in the dark and guess its a disk spindown issue, such as your cache disk being included in the list but never being able to spindown.
  6. @Kazino43 did you try the script posted above? It has been a while since i used s3 sleep with my server but the scripts on this page look correct.
  7. What kind of docker run command is created by the default template? My guess is the CMD or ENTRYPOINT doesnt do anything useful so the container immediately stops. Try running the container from the command line with the -it flag and an entry point of /bin/bash
  8. Correct, unRAID unpacks fresh from RAM on every boot. Technically speaking this item is the only one on the list that can't be done without using Docker/VM, due to the fact that unRAID does not have apt-get (or any common package manager for that matter). While this is not the only way to do things it is definitely the one i recommend. I would start by looking on docker hub for a base image of a distro you are most comfortable using, preferably an official image or one from well known maintainer (Python images are available as well). From there you have a couple of paths. You could pull the image, spin up a container and exec in, install all the extras you want in the container, then commit it to a new image for later use. Alternatively (and my preference) would be to write a Dockerfile that makes the customization to the base image as that will make rebuilding the image with new packages easier. Once you have a custom image you can either run your scripts manually from the unRAID CLI or using the user scripts plugin by spinning up a containers with the correct script. Something like docker run --rm -v /mnt/user/share-or-path-to-files:/path-in-container:rw my-custom-image /script-in-image.py --args-for-script or if you dont want to bake the script into the image docker run --rm -v /mnt/user/share-or-path-to-files:/path-in-container:rw -v /mnt/user/scripts:/scripts:ro my-custom-image /scripts/my-script.py --args-for-script You will want to look at the docker run -d and -i and -t flags as they can control if the container runs like a daemon or like a script on the console.
  9. You cannot. The unRAID OS is unpacked fresh into RAM from the flash drive on each boot. Any modifications made to the OS (read files added or changes that are not on the array) are lost on reboot. The correct way of getting something "persistent" is to either package it as an unRAID plugin or to create a script (with the user.scripts plugin) that runs at bootup and re-applies your changes to the OS.
  10. Just a quick FYI regarding the text in the above image. At this time there is no mechanism in this plugin for persisting configuration.toml across unRAID reboots. Additionally the docker service in unRAID must be restarted using the webGUI a systemctl does not exist.
  11. No idea about the statistics but i doubt that many unRAID users are using Portainer. It, like most docker GUIs, is designed for a different type of usage/workload than is typical on unRAID. That said dockerMan is a component of unRAID, so far as i am aware, and not available on other platforms. The key word is ARM. Applications (including those in a docker container) must be compiled to run on a particular architecture (x86_x64, ARM ,MIPS, etc.). There do exist docker containers that will run on ARM, however they are much less numerous at this point than x86_x64. Unfortunately i doubt that most docker containers built by the unRAID community would also have an ARM version (since unRAID does not run on ARM and multi-Arch images are tricky to do). I vaguely remember LSIO having some but you would have to head over to their forums to confirm.
  12. Not really news. You should take a closer look at the explanations of what the nvidia plugin actually does. TLDR; it does not install nvidia drivers on unRAID, rather it provides a means to install a custom version of unRAID with nvidia drivers baked in. As it is developed by a third-party, and is quite complex, a new version is not yet available. My money would by on "cpu isolation".
  13. From what i can tell when most people talk about how easy Docker on unRAID is what they are really mean is that it is nice to have a GUI to control docker rather than having to use cli and or compose files. There are a number of GUIs for Docker many of which run as a container within docker. Take a look at Rancher (both the interface and the OS), Portainer, and shipyard.
  14. No problem, this is in fact my first attempt at a plugin. I will look into containers with openvpn, but i suspect the issue may be a limitation to the way the kata runtime does things. I suspect it may be a trying to use a TAP/TUN device from the host OS, which it cant do because of the isolation, and the sandbox (VM) does not feature a usable TAP/TUN.