mArBLe

I have a couple of containers running in their own custom Docker network. All these containers need to communicate with eachother, which works fine. Now however, I need one of these containers (let's call this Source Container) to communicate with a Docker container hosted on another machine on my LAN (a Windows machine running the service in a Docker container using WSL 2). From my research I am thinking that this might be possible adding my Source Container to a macvlan network to expose it to my LAN, but still keep it on the custom network to allow communication between the other containers on that custom network. However, I have no idea how to actually implement it, and also don't really know if this is even the correct approach to solve this. Specifically what I am trying to do is an Unraid container to access my Windows hosted container to get access to the Windows machines GPU.

Did you ever solve this?

@real.ghost I have the same issue it seems. Did you ever solve this?

I have setup a VPN Tunnel using the built-in VPN Manager. I then have a number of containers using the tunnel as their network. Everything works as it should...until the VPN Tunnel suddenly stops working (I can see the connection itself stops working as the built-in PING button to the VPN server gives no response). This seems to happen after a certain amount of time, but also whenever I restart the Unraid server. As soon as I restart the VPN Tunnel, simply done by setting it as Inactive and then immediately as Active, the containers get internet access again. I guess I have two questions regarding this: Anyone else experiencing the same thing? Could I setup a script to automatically restart the VPN Tunnel if its connection is lost?

I have trouble with the DOCKER MOD for Calibre being added to the container. I have followed the documentation and added the DOCKER_MODS environment variable with the value linuxserver/mods:universal-calibre|linuxserver/mods:lazylibrarian-ffmpeg The config page in LazyLibrarian for Calibredb import program has also been set to /usr/bin/calibredb When the container is starting I get the below errors. Using the console for the same container I can with no problem access the internet (tried e.g. simply by curl ifconfig.me). I have verified the files and the /usr/bin/calibredb folder is in fact missing in the container, which of course makes the Calibre import function to fail. Any ideas why this is the case?

@quietwalker Excellent! You are welcome. Did you need to add the modprobe i915 to the Go file or did it work without that?

I finally got this working, simply by switching to the official Jellyfin Docker container. The reason for the switch was that I read somewhere that the official container uses Debian, whereas the other well known Jellyfin containers (linuxserver.io, hotio, etc.) uses Ubuntu. This made me think that some device drivers might actually be present in Debian but not in Ubuntu, for my particular hardware (Intel QuickSync via an i5-13500 CPU). As soon as I replaced my old linuxserver.io container with the official one, I only needed to add "--device=/dev/dri" to the Extra Parameters section when creating the container. After this, hardware transcoding worked straight away after enabling it in the Jellyfin control panel. Do note that I did add a line with modprobe i915 into the Go file when trying to get HW transcoding to work with the linuxserver.io and hotio containers, so this line is still in my Go file. I have not tried removing it to see if the official container still works, so you might as well try the official container without changing the Go file. If it does not work, then just change the Go file (please let us know if this is necessary or not). If you need instructions on how to edit the Go file, you can follow the below: You can edit the Go file easily by opening a terminal window directly via the Unraid GUI In the terminal window, type the command: nano /boot/config/go Add the following line at the bottom of the Go file modprobe i915 When you are done, press Ctrl + X, followed by Enter to confirm the file name, to save the file. Then restart the computer.

@robine Did you need to add modprobe i915 to the Go file? Did you need to set any specific permissions to the /dev/dri folder? I have the exact same CPU as you but cannot get Jellyfin use the Intel iGPU.

@m5B7Eu Nice! In your description I assume the NAS box is the Unraid computer? What is the purpose of your SMB share? Do you mean you export an Unraid share so you can move the data from your "download" box to Unraid? Or do you mean you add the "download" box as an external share in Unraid and essentially pull the data to Unraid? How do you handle sleep and wake of the Unraid box?

I am about to setup my first Unraid server, which will be used as a file server but also for running a couple of different Docker containers. What I am contemplating now is if it would make sense to actually setup applications such as Radarr, Sonarr and the likes on a separate low-power device which will be running 24/7 (in my case I actually have an Intel NUC 8th gen that I plan to install Proxmox on and use for running a bunch of containers that I do not want to run in Unraid, e.g. Home Assistant, as I do not want certain services to go down just because I have to tinker with the hardware of the Unraid box), whereas the Unraid box would be shutdown during the night, to save power. If using the above then of course things would have to be moved from the separate box during the day, directly to the final storage in the array as to not filling up the cache pool and then still having to wait for the mover to run. Anyone doing something similar? If so, I would very much appreciate some details.