ungeek67

Any chance we can get keepalived added to the list?

Yeah that would be perfect! Using the Folder Name as the label value is what I originally imagined when posting (dockerFolder.folderId = Downloaders) but I imagine using a unique identifier for the docker folders would make it less prone to issues? Would honestly be happy to adapt to anything, not sure how others are using the regex option but apart from the obvious *arrs nothing really works in my experience unless I just construct an ugly expression that is basically ORing container names together in which case I might as well just manually toggle them to be included.

Great plugin! Would it be possible to expand the folder regex functionality to evaluate a specific label? Will make new containers much easier to manage with less manual tasks after initial set up, especially with 6.10RC1 being more welcoming to docker compose users.

I just experienced this earlier today on 6.9.2; had to reboot and a previously working container with a fixed IP on br0 wasn’t loading via reverse proxy. Disabling and re-enabling docker made the already enabled “host access to custom network” setting actually come into effect. Been meaning to test more and look into existing bug reports. Hope that helps. Sent from my iPhone using Tapatalk

I got past this back in 6.9.0 rc2 but then stuck later on, was actually waiting for 6.9 to start this thread back up! Make sure your settings json file is placed correctly, the container is starting with the arguments for "job_name" but no folder and/or config exists and you can't interactively send the "y" I used the job name "unraid_data_spotlight" so my config looks like: fscrawler docker post arguments (--restart commented out after first run) fscrawler unraid_data_spotlight #--restart /mnt/user/appdata/fscaler/unraid_data_spotlight/_settings.json --- name: "unraid_data_spotlight" fs: url: "/mnt/user" update_rate: "15m" ... I think thats all I did to get it moving awhile back, let me know if that doesn't help and I'll blow away my current setup and do it again and actually take notes this time. My issue is that all the tests are passing, including mdfind which is returning the expected results. But when I then try to use spotlight on macOS Big Sur I get either nothing. mdutil -s /Volumes/media returns "Server search enabled" as expected. Adding "elasticsearch:index = unraid_data_spotlight" to the samba extra config under [global] hasn't helped either. Anyone get beyond this?

Would love to be able to create a custom/informative motd, any objections to including update-motd? If possible figlet and lolcat too but they're really only for a bit of 'fun' for a header if I'm pushing my luck.