Donrenegade

Thank you, this helps with most of the disk usage for Jellyfin! Quick tests show me that less data is being kept. So this has mostly helped me out. I feel more confident using this. I do have more use-cases for using /dev/shm . Uploads of files for certain applications cause a reverse proxy like NPM to temporarily write to disk, and by default even in the docker.img. I want to change this to /dev/shm as well and i can still think of more use cases that this would be preferred and so the question still remains: Is there any way that only /dev/shm can be backed by a pagefile? Or is there any other solution for this?

Ok so I've been using Unraid to host my own Jellyfin instance. I've ripped my Blu-ray collection and now I have dozens of ripped movies of around 50GB. I share these movies using Jellyfin with a couple of family members. Now sometimes these movies have to be transcoded or repackaged, reasons are irrelevant. By default this is done in the config folder in appdata on my cache drive. This can cause lots of writes and therefor wear to my SSD's. Solution I've found on the internet: use /dev/shm to transcode in RAM. This sounds great, but I'm still hesitant to set this up. This RAM-disk has a capacity of half of the system RAM, in my case it's 32GB for the RAM-disk. Repackaging multiple Blu-ray rips at the same time quickly fills this up. What happens if it's out of memory? Will it just crash the application or is there physical storage on SSD that it will overflow to? I've been looking at the pagefile plugin, but this seems to be for all RAM. I only need it for the /dev/shm folder. What solutions are there or is there any setup that allows me to: A - fill up /dev/shm, and B - overflow only to physical SSD storage? I'd like to keep regular RAM usage for containers and the system itself separated from the RAM-drive and not to be impacted by pagefile or anything like that.

I'm not sure whether this is the intended way to do this, but adding the following has fixes my issues: Unraid => Docker => Under Docker Containers, select container and edit => Enable Advanced View ... Under Post Arguments, I added the following: && docker exec -u root homeassistant sh -c "chmod a+rwx /dev/zigbee" The device can now be accessed without needing privileged mode!

Hello! Fairly recently I've started using the docker functionality within unraid. I'm having problems with permissions from within a docker container and i'm a novice at both linux and docker itself. I'm trying to pass through a usb device to my container by id, rather than by "usb device". Because when I do that, it (seemingly) randomly switches from location "/dev/ttACM0" to "/dev/ttACM1" and vice versa. So passing through by id appears to be the way forward. Now i'm passing through a device by id using the following value: /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230807104003-if00:/dev/zigbee Within the container itself, the device now has the following permissions "crw-rw----". With these permissions, the application within the container cannot access the device. When i manually edit the permission within the container using the following command: chmod a+rwx /dev/zigbee , the application can acces the device without any problems. The issue with this is that whenever the container is restarted, the permissions obviously get reset. Setting Post Arguments only seem to execute on the host machine, but maybe i'm missing something. How can i "permanently" change the permissions for the passed through device on "/dev/zigbee"? As a note: running the container in privileged mode also allows the application to use the device, but i'm trying to avoid that for obvious reasons.