linuxserver.io

Application Name: mStream Application Site: https://mstream.io/ Docker Hub: https://hub.docker.com/r/linuxserver/mstream/ Github: https://github.com/linuxserver/docker-mstream Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

Application Name: Kanzi Application Site: https://lexigr.am Docker Hub: https://hub.docker.com/r/linuxserver/kanzi/ Github: https://github.com/linuxserver/docker-kanzi This release is a little bit special as the application author is actually an Unraid user, so you all have @m0ngr31 to thank for this awesome Alexa skill to enable voice control with Kodi. Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

Application Name: Quassel-Web Application Site: https://github.com/magne4000/quassel-webserver Docker Hub: https://hub.docker.com/r/linuxserver/quassel-web/ Github: https://github.com/linuxserver/docker-quassel-web Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

Application Name: nntp2nntp Application Site: https://sourceforge.net/projects/nntp2nntp/ Docker Hub: https://hub.docker.com/r/linuxserver/nntp2nntp/ Github: https://github.com/linuxserver/docker-nntp2nntp Please post any questions/issues relating to this docker you have in this thread. Warning Whilst we know of no nntp2nntp security issues the upstream code for this project has received no changes since 06.08.15 and is likely abandoned permanently. For this reason we strongly recommend you do not make this application public facing and if you must do so other layers of security and SSL should be considered an absolute bare minimum requirement. We see this proxy being used primarily on a LAN so that all of the users NNTP applications can share a common set of internal credentials allowing for central management of the upstream account e.g change provider, server, thread limits for all applications with one global config change.

Don't feel dumb. It's an issue with the forum, you can't be expected to know that.

Application Name: Sickchill Application Site: https://sickchill.github.io/ Docker Hub: https://hub.docker.com/r/linuxserver/sickchill/ Github: https://github.com/linuxserver/docker-sickchill Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

Application Name: Taisun Application Site: https://www.taisun.io/ Docker Hub: https://hub.docker.com/r/linuxserver/Taisun/ Github: https://github.com/Taisun-Docker/taisun Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, rather use the linuxserver.io forum for support.

Application Name: Grocy Application Site: https://grocy.info/ Docker Hub: https://hub.docker.com/r/linuxserver/grocy/ Github: https://github.com/linuxserver/docker-grocy Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

I mapped the ports according to the info here. https://help.ubnt.com/hc/en-us/articles/218506997-UniFi-Ports-Used I left out 6789, 27117 & 5656-5699 as they are require for mobile speed test, local bound database & EDU products respectively.

This container is a drop in replacement for our previous Unifi container. We have taken the decision to produce a new container rather than update our old container to mitigate the fact that there is a massive change in what version you will be pulling if you use the latest tag. Our new container allows the use of the following branches. Warning! The latest tag may be broken or buggy (and often is!) latest - The most recent build version of the Unifi controller software, regardless of release train. LTS - The most recent Long Term Support release. 5.9 - The most recent 5.9.x release. 5.8 - The most recent 5.8.x release. 5.7 - The most recent 5.7.x release. In our previous container, latest would pull the most recent LTS release, so if you wish to ensure continued stability, you should choose to use the LTS branch of this container. The appdata is fully compatible with your old appdata, however if migrating from our old container and you wish to use your existing appdata then please note you will need to manually select your old unifi appdata folder. As always you should ensure you have backups before migrating. (Regular backups of appdata being recommended general maintenance in any case) This is completely by design, to ensure no inadvertent overwriting and massive version hopping which would be the outcome if we had decided to modify our previous container. Before you attempt to migrate, ensure the old unifi container has been stopped/removed. To select your old appdata folder, first click Show more settings Click in the appdata box. Go up a folder level by clicking in the box shown below. Finally select your old appdata folder. (Reminder, make sure you've made a backup)

Application Name: Unifi-Controller Application Site: https://www.ui.com/software/ Docker Hub: https://hub.docker.com/r/linuxserver/unifi-controller/ Github: https://github.com/linuxserver/docker-unifi-controller/ Please post any questions/issues relating to this docker you have in this thread. If you are not using Unraid (and you should be!) then please do not post here, instead head to linuxserver.io to see how to get support.

Now that's said and done, lets move on to the bits you're all interested in. Please note that hardware (GPU) enabled transcoding requires either a Plex Pass or Emby Premium subscription. Note: Emby will both decode and encode using the Nvidia GPU, Plex currently only encodes. nvidia-smi requires a compatible video card - Some older nvidia cards are incompatible, sorry nothing we can do about that, everything will work apart from using watch nvidia-smi to view transcoding processes. Step 1 Install the Unraid-Nvidia plugin from Community Applications or alternatively manually by copying this into the plugin page. https://raw.githubusercontent.com/linuxserver/Unraid-Nvidia-Plugin/master/plugins/Unraid-Nvidia.plg Step 2 Select the version of Unraid you wish to download and click the download and install button the reboot your server Step 3 Go back to the Unraid-Nvidia page and you should find the information on Nvidia graphics cards is populated like below. There are three pieces of information for each card, looking at GPU 0, you can see the GPU name, the bus location and the GPU UUID. Before you start, copy and paste the GPU UUID somewhere handy, or keep the Unraid-Nvidia screen open in a separate browser tab as you'll need it shortly. How to Utilise the GPU in a Docker Container Now to utilise GPU 0 in a docker container, lets look how to do so using the LinuxServer.io version of Plex, (although this can be applied to any container). Add or edit Plex as per normal and switch the template to advanced mode. Now add --runtime=nvidia to Extra Parameters: and then switch advanced mode off again. Now we need to add two extra parameters, the first is the easiest one, as it will be identical to all containers. Click on Add another Path, Port, Variable, Label or Device and change config type to variable. then add in the KEY field NVIDIA_DRIVER_CAPABILITIES and in the VALUE field add all Now the 2nd parameter to add do exactly the same process as before but in the KEY field add NVIDIA_VISIBLE_DEVICES and in the VALUE field add the GPU UUID of the card you want to use. Configuring Plex Go to your server settings and configure like below. and you should find when playing content that is being transcoded you get a hw indication in the webui like below. and running watch nvidia-smi from the terminal shows the transcoding process Configuring Emby Go to your server settings and configure like below. Now you should find when playing content that is being transcoded it shows in the webui like so. and running watch nvidia-smi from the terminal shows the transcoding process That's it. Have fun.

Read this first 1. Any posts discussing circumvention of any Nvidia restrictions we will be asking mods to remove. We have worked hard to bring this work to you, and we don't want to upset Nvidia. If they were to threaten us with any legal action, all our source code and this plugin will be removed. Remember we are all volunteers, with regular jobs and families to support. Please if you see anyone else mentioning anything that contravenes this rule, flag it up to the mods. People that discuss this here could potentially ruin it for all of you! 2. If you attempt to start a VM passing through a GPU that is actively transcoding, you will hard lock your server and it will need an unclean shutdown. 3. If you use Unraid in GUI mode and have only a single GPU in your server and you use that GPU in a virtual machine, trying to start that VM will crash libvirt. 4. You can passthrough a GPU that is being passed through to a docker container as long as when you start that VM there is no active transcode processes happening, the docker container will fallback to software transcoding. Check the webui of the docker container to check if transcoding is occurring before starting the VM, or if your GPU supports it, you can use watch nvidia-smi to check for transcoding processes. 5. To be 100% safe, we recommend a dedicated GPU for transcoding that is not being used for any virtual machines, if you decide to ignore this, then you're on your own, we are not responsible for any problems that ensue. 6. We will produce one Nvidia build per Unraid release, we will not be updating the drivers multiple times for each Unraid version, unless there is a critical bug that demands this. So please don't ask. 7. We are reliant on a lot of upstream projects here, we don't have any control over them, so we can't guarantee this will work for every release. 8. We will look at a DVB solution in the future. Once we know this is stable and working. Background Unraid Nvidia is a way of leveraging a Nvidia graphics card in your Unraid server to offload transcoding from the CPU to your GPU. Although people have long been asking for Nvidia drivers on Unraid, there seems to have been a lack of understanding that this wouldn't solve a fundamental problem. It would mean that only processes run on the host would be able to use them, they wouldn't be useful within docker containers unless the same drivers were then installed within each container, which is both inefficient and requires a special build of every container you wish to use Nvidia within. We began to look at a possible solution about 5 months ago and it has required a number of different steps to get this working. 1. Installing Nvidia drivers and kernel modules into Unraid utilising upstream SlackBuild packages, namely nvidia-kernel, nvidia-driver, google-go-lang, libseccomp & runc. Modifying a part of the nvidia-driver due to the lack of a desktop environment on Unraid. 2. Modifying the docker runtime to a version that can use an Nvidia wrapper to enable any docker container on your system to use the Nvidia graphics card using the Nvidia docker project. 3. Rolling all this together and completely repackaging Unraid to implement all these changes, only bzroot-gui is left unaltered. 4. Development of a plugin to enable easy downloading of the modified Nvidia release of Unraid. All in all, not a simple task. Initial attempts by @CHBMB were hindered by segfaults, at which point, his real life commitments took over and the project hit a hiatus, @bass_rock then forked the work and hit the same issue. After reaching out bass_rock we invited him to join the LinuxServer.io team to collaborate and to try one final strategy we had in mind to get this working, but hadn't got around to. This strategy was instead of installing the drivers at boot time from a custom built Slackware package, taking the approach at build time of unpackaging bzroot and installing the drivers directly there, removing the need for an install at boot time and to our delight solving the segfault issue. Enthusiastically bass_rock implemented this and also made the original scripts nothing short of a work of art, adding shine and polish.

Plugin Name: Unraid Nvidia Github: https://github.com/linuxserver/Unraid-Nvidia-Plugin This plugin from LinuxServer.io allows you to easily install a modified Unraid version with Nvidia drivers compiled and the docker system modified to use an nvidia container runtime, meaning you can use your GPU in any container you wish. Any posts discussing circumvention of any Nvidia restrictions we will be asking mods to remove. We have worked hard to bring this work to you, and we don't want to upset Nvidia. If they were to threaten us with any legal action, all our source code and this plugin will be removed. Remember we are all volunteers, with regular jobs and families to support. Please if you see anyone else mentioning anything that contravenes this rule, flag it up to the mods. People that discuss this here could potentially ruin it for all of you.

**Attention -Latest Update - Image Rewrite** We have rewrite to our newest image, so much more lightweight, supports theme folders, fixes a known shutdown bug. Please make sure you backup your appdata before updating in case of any issues.