This command returned: WARNING: java.io.tmpdir directory does not exist But nevertheless the output after inserting the license was again a successful activation. I will try it with new media. Edit: Error message still there: FileBot requires a valid license. Please run `filebot --license *.psm` to ...

I just follow the instructions meticulously: After the container ist set up, I run the command as root docker run --rm -it -v data:/data -e PUID=1000 -e PGID=100 rednoah/filebot --license in the CLI. Then I paste in the License text with PHP signature. I receive the "activation successful" message ...

Well, this led to the aforementioned "successful activation"... But, after dropping some files in the following happend: Whoopsies! --action COPY requires a valid license. * Consider using --action TEST License Error: UNREGISTERED ________________________________________________ / Please purchase a ...

After some trial and error docker run --rm -it -v data:/data -e PUID=1000 -e PGID=100 rednoah/filebot --license and entering the license gave this result: Initialize Cache folder: /data/filebot/cache Initialize Logs folder: /data/filebot/logs Initialize TemporaryFiles folder: /data/filebot/tmp ...

Hi there somehow filebot-watcher in Docker lost the license. After re-composing and entering the container and trying to add the license the following error occurs: filebot --license -e PUID=1000 -e PGID=100 WARNING: java.io.tmpdir directory does not exist Did you read the manual? └ https://www.f ...

So, I threw a few files into the input folder and now everything works as expected and with correct permissions. I want to point out that you have to use quotation marks and start with a slash when you use the --def movieFormat in Docker Compose (maybe you can add this to the documentation @rednoah ...

Yep, thanks for the hint. Had a Image from August. Just pulled the latest, got an error when using the line user: 1000:100 (sudo: you do not exist in the passwd database). Swapped back to " environment: - PUID=1000 - PGID=100" and now filebote-watcher setp up watches again. Now in the data folder is ...

Ah, yes, I was using -- action COPY. Nevertheless user: 1000:100 was accepted by your container. There were some errors due to permission within the data folder which contains the filebot files. An unexpected error occurred during startup: Access Denied: Cache directory is not writable: /data ...

Thank you for your answer. I don't understand what the link you provided is about. For a more complex amc-script syntax I'll try the .env- or args.txt-way in the future, I think. When I inspect the docker container filebot-watcher the changes to your ENV lines are correctly implemented. Env 0 PUID ...

So, I finally figured the correct code for Docker Compose out volumes: - /Data/Docker/FileBot2:/data - /Data:/volume1 command: /volume1/Downloads --output /volume1/Media -script fn:amc --def movieFormat="/volume1/Media/Movies/{n}/{n} ({y}" seriesFormat="/volume1/Media/TV Shows/{n}/Season {s.pad(2 ...

So I figured out, that the filebot-watcher docker lacks some features. It runs with root, something like environment: - PUID=1000 - PGID=100 didn't work as expected. I tried to cut the docker compose as much as I can and abandoned the args.txt-way. Without any arguments filebot-watcher works (very ...

Somehow it still doesn't work as expected. I found the logfile in a total different folder. It sits in the Docker-subfolder for some reason /Data/Docker/FileBot2/.filebot/logs/--log-file /volume1/Media In my Docker Compose text the volumes are defined by this volumes: - /Data/Docker/FileBot2:/data ...

Hi there I installed filebot-watcher via Stacks in Docker. Filestructure is /Data:/volume1 and command is /volume1/Downloads --output /volume1/Media @/volume1/Media/args.txt (which contains --def movieFormat=Filme/{emby} seriesFormat=Serien/{emby} musicFormat=Musik/{emby} --action COPY) In the logs ...