sir_storealot

Thank you! The plugin has been fantastic, super stable and issue-free, so I hope I can continue using it without Lime breaking anything with their TS integration.

After 7.0 update I still seem to be using separate TS plugin (this). Thought this was somehow integrated? Anything I need to do?

I have created a dedicated UID/GID for this container, and trying to run it with those by setting UID and GID container variables to what I created (1500). However, these seem to get completely ignored, the container always starts as my main unraid user. I also tried using docker extra arguments "--user 1500:1500" but then the container does not start. Any advice on how to set the runtime user?

Hey, not sure I understand all this correctly, but nevertheless krusader is currently my largest container with around 2.6 GB. Quite suprising for such a tool that certainly looks and feels "lightweigth". Is there anything I can do to reduce this size? Or are there similar NC type options that anyone would recommend that have a smaller footprint?

I really like this plugin, it is very useful! However, I find I have to constantly increase the zoom level of my browser when editing the compose or environment files. Is it possible to somehow increase the font size in the built-in editor? Currently the font of the editor is significantly smaller than the rest of the Unraid GUI text, which forces me to zoom in each time.

Just one strange thing that I noticed: my backup reported an error d/t missing docker path (as described above), but the post-run-script still got called with TRUE as the 3rd argument, indicating a successful backup. Isn't that odd?

You are missing the point, this is not about backing up "valuable data". It's about getting rid of the error message (i.e. ignore the volumes) and allow the backup to finish without throwing an error. The volumes ARE disposable (at least in my case). Well... Just because you cannot think of a use case, doesn't mean it does not exist for others. You can read up on the general advantages here: https://docs.docker.com/storage/volumes/

Ah interesting, I'm facing the same issue. Would be nice if volume mounts (mappings with no leading slash) would be ignored. Not true at all. Volume mappings work fine with the docker compose plugin, and in fact once created (with the plugin or the command line), also with the unraid vanilla interface. Volumes are the preferred docker way of storage, and they are very useful on unraid in certain use cases.

I totally feel you. Hope this will get some good answers on the Unraid side, would be interested myself. However, as far as the IoT devices are concerned, did you think about assigning them to their own wifi network which has client isolation and only (NAT) outside access (kinda like DMZ)?

Awesome, thank you so much! Makes my scripts a lot cleaner!

@SirCadian glad it is working fine for you! You actually inspired me to do a little experiment regarding deduplication efficiency of the Appdata Backup output. Test scenario: Appdata Backup Full flash + VM meta (1 VM) + docker config backup (13 containers), AB compression disabled This is then backed up to an external repository using (a) restic and (b) kopia to compare the two, including best-speed deflate compression. AB Backup 1 taken at t0 (source dir size 1552 MB) AB Backup 2 taken at t1 = t0 + 24h (source dir size 1548 MB) Normal system/container usage during the 24h period, nothing special. Note the 2nd backup is slightly smaller, maybe some logs inside containers got deleted, database trimmed or whatever. Results: Repo size (MB) after 1st backup: 1038 kopia 988 restic Repo size (MB) after 2nd backup: 1291 kopia (+253 MB) 1086 restic (+98 MB) Results - Variant "untarred": I also did a test (with fresh repositories) untarring the the appdata backup tars (and then deleting them), to see if backing up the raw files improves deduplication, and it did: kopia untarred size increase t0->t1 154 MB (99 MB less) restic untarred size increase t0->t1 75 MB (23 MB less) My takeaway: As long as the Appdata Backup compression is turned off, deduplication will work ok. For best deduplication, the files need to be untarred. Could be an interesting addition for the AB plugin to add an option to just copy files instead of tarring. Notes: Flash backup was still compressed all the time, did not want to mess with this.

You make some excellent points, and I agree 100 % with your risk assesment. However, I believe I have already tighened all the "other screws" that you mention a long time ago, with docker containers from non-official sources (hard to judge what really is "reputable", it's always a grey area) now being the 2nd biggest exposure I can see, which is why I am so nervous about it. The biggest exposure in my eyes are Unraid plugins... But it's so hard to live without them. As always, a trade-off needs to be made between security and convenience... @jlh Thanks for your additional in-depth explanation. Really great to see you guys are on top of this!