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?