Hi,

to help others which might have the same issue. For some reason the entrypoint was not correct. It was "filebot" instead of "/opt/bin/filebot-watcher"

I hope this helps someone else.

Kind regards
socram

Thanks for your reply! It does not really kill itself, it runs through perfectly fine and ends with "Done ヾ(＠⌒ー⌒＠)ノ" Then, the container stops. For now, I am using watchmedo to trigger on new items which then starts the container, however, that's not a perfectly nice sulotion since I have ...

Hi, I am using docker for a while now and switched filebot to docker. The docker:watcher works fine so far, but it is killing itself after one run. Most likely, I just misconfigured something: My .env: LOG=/data/amc.log UNSORTIERT=/volume1/Multimedia/Downloads/unsorted/{file.structurePathTail} SERIE...

Ok, that makes sense then, thanks. However, with the parameter /volume1/Multimedia/Downloads/extracted (which is my default extraction path) filebot watcher unfortunately does not perform the job. This is what the log says: Waiting 90 seconds for changes to settle down... Modified: /volume1/Multimed...

For some reasons, the variables do not work in the @file implementation. However, copying the line in instead of the variable did the job. Thanks a lot for your support and your really fast reply!

Dear all, I read the FAQ already, however, this is a very simple question and therefore can be explained quickly: I use the following environment variables for sorting series and movies (since pasting the whole entry would lead to serious escaping what I wanted to prevent): https://pastebin.com/fw4e...