docker filebot node unpacking issues

[turtlejay]

im having issues using filebot node in docker unpacking files after being called by qbittorrent via curl.

best i can tell all permissions are set properly:



errors on execute:

Code: Select all

Read archive [kevin.smith.silent.but.deadly.extended.edition.2018.720p.web.h264-opus.rar] and extract to [/volume1/complete/Kevin.Smith.Silent.But.Deadly.Extended.Edition.2018.720p.WEB.h264-OPUS/kevin.smith.silent.but.deadly.extended.edition.2018.720p.web.h264-opus/Kevin.Smith.Silent.But.Deadly.Extended.Edition.2018.720p.WEB.h264-OPUS]
Access Denied: /volume1/complete/Kevin.Smith.Silent.But.Deadly.Extended.Edition.2018.720p.WEB.h264-OPUS/kevin.smith.silent.but.deadly.extended.edition.2018.720p.web.h264-opus
File does not exist: /volume1/complete/Kevin.Smith.Silent.But.Deadly.Extended.Edition.2018.720p.WEB.h264-OPUS/kevin.smith.silent.but.deadly.extended.edition.2018.720p.web.h264-opus

container was setup as follows:

Code: Select all

services:
  filebot-node:
    container_name: filebot-node
    image: rednoah/filebot:node
    restart: unless-stopped
    volumes:
      - /share/Data/FileBot:/data
      - /share/Data:/volume1
    ports:
      - 5452:5452

docker running on ASUSTOR AS5304T. 64bit Linux effectively

[rednoah]

Access Denied strongly suggests it's a permission issue. filebot cannot do what the OS (or the OS inside the docker contain) does not permit.


How did you confirm that all permissions are set properly? (NOTE: the screenshot you posted does not show any file permissions)


Have you created a test folder with sample files so you can try different things? Is everything not working, or just extracting archives?


What are the permissions of your test folder and files within? Who is the file owner?

Code: Select all

ls -l

What user ID are you running as? What user ID do you want filebot to run as?

Code: Select all

id

EDIT:

You can do PUID=0 to run filebot as root (inside the container) to possibly work around your permission issues, but also possibly cause more permission issues:
https://github.com/filebot/filebot-dock ... erent-user



EDIT 2:

This error probably means that the script tries to extract the archive into a new folder but can't create that new folder:

Code: Select all

Read archive [...] and extract to [...]
Access Denied: ...

[turtlejay]

ive ditched node for watcher with exact same permissions and so far have had no issues with the same folders. odd. node worked sometimes but not others. the puid and pgid are set to an administrator id that has full access to the entire system. i assumed (wrongly possibly) that this set permissions properly.

[rednoah]

That should work. PUID is 1000 by default so I wasn't sure if you set it explicitly or just left it at the default value. That doesn't set any permissions, but if that user has read-write-permissions for your input and output folders then it should work. I'd be worried about getting different results with different containers though, since they should work exactly the same, so we're probably missing something.

[turtlejay]

i ended up creating the container giving filebot the id of 999 which is the administrator group. everything works flawlessly now. thanks for the help. now on to rtorrent