The error is actually correct (although I haven't seen it), as ...helpers.php
$unraid = parse_ini_file("/etc/unraid-version");
which means that the line in question should be ..tuning.php
version_compare('6.8.3', $unraid['version'],'>')
The "@" sign signifies that it's a symbolic link. The actual directory is /mnt/remotes/DROBO_MUSIC
I've had the odd problem (read that as every container that I'm using with SMB shares) where if in the template I reference /mnt/disks/shareName it doesn't actually work within the container, but if I reference /mnt/remotes/shareName it does.
I don't have time until late February to really investigate what exactly is going on and if there is another flag you can use on the mapping to alleviate this.
Once you give the app a static IP, all port mappings are ignored as they are at that point irrelevant. You just forward the applicable WAN port to the applicable LAN port for the IP
I think you need @JorgeB.
The way that I see it, btrfs usage shows ~931G of total space on the cache pool, but df is reporting that the size is only 466G, and this is playing havoc with the docker.img file.
Done. I don't really see why you'd want this though as there's absolutely nothing that can be edited via the xml that can't be done via the template screen, except for any internal CA elements.
It's already a known issue, and relatively minor since the usage of "Template Repositories" is rare (due to CA), and easy work arounds -> either switch to master branch or place the xmls on the flash drive.
You *might* want to also consider looking at something akin to https://forums.unraid.net/topic/91450-alexa-unraid-voice-control-how-to/
(Although its geared towards Alexa, but the concept is the same. Drop a file into dropbox and have the server act upon it). No CSRF's involved assuming you can upload a file from your app to drop box, and you'd be able to start / do anything you want at all.
Your problem is that the xml is in the "main" branch. dockerMan only supports the "master" branch. (For repositories, CA supports both main and master)
The PR for the help text hasn't been merged yet @SpencerJ
The setting itself is for when the docker service is stopping the amount of time the system waits for a graceful shutdown (in seconds) of the container before the system forcibly kills it.