Renegade605

Hi there, having an issue with a couple NFS remote mounted shares. Server 1 is a Dell workstation on v6.9.2 and server 2 is an HP DL380 G7 on v6.10.1. Shared folders mounted on one Unraid box from the other one (in either direction) get mounted as read-only. Attempting to copy any file to it results in cp: cannot create regular file '/mnt/remotes/tv/custom.list': Read-only file system Server 2 has a different NFS share mounted from a Dell EMC SAN with no writing issues. Logs from mounting: Jun 5 15:01:42 EDI unassigned.devices: Mounting Remote Share '192.168.0.1:/mnt/user/tv'... Jun 5 15:01:42 EDI unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,noacl '192.168.0.1:/mnt/user/tv' '/mnt/remotes/tv' Jun 5 15:01:42 EDI unassigned.devices: PHP Warning: chmod(): Read-only file system in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 2059 Jun 5 15:01:42 EDI unassigned.devices: PHP Warning: chown(): Read-only file system in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 2060 Jun 5 15:01:42 EDI unassigned.devices: PHP Warning: chgrp(): Read-only file system in /usr/local/emhttp/plugins/unassigned.devices/include/lib.php on line 2061 Jun 5 15:01:42 EDI unassigned.devices: Successfully mounted '192.168.0.1:/mnt/user/tv' on '/mnt/remotes/tv'. Subnet 0 is a direct link between servers with no other devices or switches/routers. But, attempting to mount the share on subnets 1 or 2 has the same result.

Can I allow a Docker container access to read/write a file on the flash drive? Specifically one in /boot/config/plugins/... chmod has no effect, and attempting to find ways around directly modifying the file came up empty.

Yes, I'm aware of that. I'm asking what other ways I can toggle on or off the update. Can I give a Docker container write access to the settings file? If so, how? chmod doesn't seem to do anything.

I'm looking for an option to have a container autoupdate most of the time, but not all of the time. For context, the use case is homeassistant updates are on a frequent minor revision with bug fixes and a monthly major revision with potential breaking changes. I'd like to have the autoupdate on while the latest version is only a minor revision but off when it's a major revision so I can manually review the breaking changes before updating. I've already figured a way for homeassistant itself to see a new version available and decide if autoupdate should be allowed or not. My plan was to have it modify the contents of "/boot/config/plugins/ca.update.applications/DockerUpdateSettings.json" to turn on/off the autoupdates. I can confirm this works by editing the file through the terminal, but I've been unable to give a docker container write access to this (or any) files on the flash drive. If someone knows how to achieve this, my problem is solved please let me know how. Failing this approach, is there another way that I can toggle the settings? My docker container can make http requests, send tcp or udp packets, connect via a websocket, and probably many more through extensions if there's a good way to accomplish this. It can also execute shell commands, but as far as I know that won't help because the shell will be jailed. If I'm wrong about any of this, please let me know. Basically if anyone has any idea how I could do this, please let me know. Side note: when editing the DockerUpdateSettings.json file, I noticed that setting a container '"update": false' makes the settings page show that the container is not autoupdating, but it still does. To stop it, the entire key must be deleted from the file. I'm sure this isn't high priority since you aren't intending for anyone to edit this file directly, but I thought I'd let you know anyway.

Hello, I have a visual bug to report. If the available memory of the containers in a folder are limited to different quantities, the folder will show max RAM as the amount allocated to the last container in the list. Instead, the value shown should probably be the combined total of all containers in the folder, up to a maximum of the total system RAM.

Hi folks, I also recently noticed the flash drive corruption warning. In my case the warning is noted in "/boot/config/plugins/iscsi-initiator/targets.cfg". Contents of that file are: Before attaching diagnostics, do I have to worry about stripping any information?

Hello, I've been using this plugin without issue for several months, but last night I ran into a problem. My weekly backup happened to go at the same time that a parity check was running, this caused the backup to run so slowly as to still be running 5 hours later when I woke up (and so all my containers were still shut down). I paused the parity check and the backup and auto-update completed within 20 minutes. I suggest a solution to this would be an option that would allow us to select what to do if the scheduled backup time arrives and a parity check is also running. Likely options should be pause parity check and resume after, skip backup, delay backup, perhaps more options. I looked for an option like this but I couldn't see one. Cheers!

Came here to add that I am also using NPM, with different config options that work fine. "gzip off;" in the advanced tab seems to be the only setting that matters, as I have different SSL settings and cache assets and block common exploits on. I also tried using "location /plugins { gzip off; }" kind of in line with OP's solution for Caddy, but this caused the entire docker page to get stuck with the Unraid loading icon forever. I can't find anything online to indicate that disabling gzip for the entire Unraid proxy has any downsides, so I'm going to leave it that way. Also, a hearty second to all the thanks to the folks who stuck with this and solved the problem. I would have knocked off and ended this discussion long before OP did. These "you're doing it bad and you should feel bad" responses were on an entirely different level than friendly advice, which unfortunately happens quite often in these forums. Did I mention I never let any of my disks spin down? Oops, here comes a flame war on a 3 year old thread! 🤐