sephallen

This is not something I had considered, though I am sure Alpine does have some i386 compatibility but I cannot vouch for it. I would not like to go back to the days where unRAID went from 32-bit to 64-bit and we had essentially zero 32-bit support for some time 😬

I would say unRAID OS is almost certainly lighter than Ubuntu server - it only ships with what it needs to perform as a NAS. Though I am not saying Ubuntu could not be stripped back to the bare bones too, however I can imagine it would be a lot of work to create and maintain. unRAID is not designed to be a full featured server or to be exposed to the internet. I can't imagine this ethos changing anytime soon. As for unRAID becoming an application, this does sound cool but I believe unRAID ships with a custom build of the Linux kernel. One of the reasons why unRAID is so stable as is able to do what it does is because of the level of access it has to the entire system. I think what you are describing / wanting might already be possible with ZFS or software RAID solutions installed on something like Ubuntu.

Debian could be pretty nice due to its stability and LTS policy. Rocky Linux could also be a good alternative. However, due to the somewhat immutable, light-weight unRAID OS which is designed to be booted from a USB flash drive, perhaps something like Alpine would be better suited.

I like this solution a lot - I too have a MikroTik router, I think I will need to have a play around with this!

You can set up some routing via the UI by navigating to: Settings -> Network Settings and scrolling down to the "Routing Table" section at the bottom. I'm not sure if this will fit your needs though!

Updated title as this is still an issue for me in the latest release of unRAID (6.12.6).

I've had this same issue for quite some time: but I have never been able to crack it by setting different static routes. The strange thing is, it used to "just work" but was broken by an unRAID update some time ago. If you ever figure it out, I'd love to know you you do it!

The repo already contains a docker-compose.yml template. If you clone the repo onto your server and run docker compose up, you should be good to go.

I always choose SAS over SATA for two main reasons: 1. The SAS interface is full duplex 2. In my experience, SAS drives tend to last longer

Since upgrading from 6.10, I have no longer been able to access the WebUI of any containers which utilise my "VPN tunneled access for docker" WireGuard (wg0) network when VPN'ed into my home network. VPN access to my home network goes via my router (running RouterOS) and not via unRAID directly. I have both an OpenVPN and WireGuard servers running on my router and neither is able to connect to these container WebUIs. I suspect this issue has something to do with being on a different LAN / subnet to my unRAID server while VPN'ed into the network. This is because I am able to remote into a VM running on unRAID (which is on the same subnet as the unRAID server) via my VPN and then browse to a container WebUI (on the wg0 network) using the VM's browser and it is accessible. I have tried playing around with static routes on my router, but sadly nothing has helped thus far. It used to work with no issues on unRAID 6.10 - is this a new bug introduced in 6.11?

Forgive me if this has been asked before, I did search the forums and Google, but I am coming up short. I have imported my WireGuard conf (AirVPN) and the peer type of access is set to "VPN tunnel for docker containers only". The tunnel appears to be connected and working, but the wg0 custom network does not appear in the drop down list of network options in the container settings. It also does not appear when running docker network ls I have restarted the docker service and recreated the WireGuard tunnel a few times, but this does not seem to help. I am running unRAID 6.10.3. Have I missed something obvious?

No worries, I'm glad someone else was able to find it useful. The container should persist after a reboot, but if you were to recreate your docker.img, you would need to find and run the command again. If you used the docker-compose template, you could simply run: docker-compose up -d within the same directory as the template to recreate the container (though you would need the docker-compose CLI tool installed on your unRAID machine).

Hi guys, the simplest way to get storman up and running would be to use this command: docker run -d --privileged --name storman -p 8443:8443 nheinemans/storman and then navigate to https://your-unraid-box:8443 (https is required, but it is using a self signed certificate, so you'll get a warning in your browser). The login credentials are root:root. If you preferred something a little more persistent, you could create a docker-compose template like this: version: '3.4' services: storman: image: nheinemans/storman container_name: "storman" privileged: true tty: true ports: - "8443:8443"

When EC28 mentioned they had started from scratch, it reminded me that I had done the same over the weekend in order to try to fix the timeouts I often get (particularly when downloading larger files), but alas it didn't fix the issue. However, I also changed a setting in my rtorrent.rc and hadn't restarted yet - turns out the value was invalid and that's what the issue was. I have now corrected it and everything is working fine again. So AirVPN is a red herring - thanks for the help and sorry for wasting your time!

I'm having the same issue as you and I am also on AirVPN. I even tried rolling back a few versions of the docker image, but the same issues persists. I assume it must be AirVPN related. Generating new OVPN files from AirVPN (trying UDP and TCP) didn't solve the issue either. I will keep restarting in the hopes that my set up will magically start working too I guess!

I've been leaving my Plex docker running for hours (2-3+) on both plexpass and latest and I am still unable to access the Plex UI. Strangely, the log is also empty. This also happens if I try a clean install with an empty settings directory and after deleting the docker container and image UPDATE:: After clearing out the container and image again and a few more restarts, I managed to get the "latest" non Plex Pass version up and running.