Page 1 of 1
[Terramaster NAS permissions] Docker issue with excludes
Posted: 25 Feb 2025, 12:53
by HarveyBirdman
Hi, long time user and big fan of the app! Am setting up a more automated workflow in docker on my NAS and the last step is to get filebot to work on it. This is the command in the .yaml file -
Shell: Select all
version: '3.3'
services:
filebot:
container_name: filebot-watcher
image: rednoah/filebot:watcher
restart: unless-stopped
environment:
- PUID=1000
- PGID=1000
volumes:
- /Volume1/Plex/Downloads:/downloads:rw
- /Volume1/Plex/Media:/media:rw
command: /downloads --output /media
The main error seems to be about .excludes and I've searched through forum but can't see how to either tell it not to look for excludes, or create the excludes file manually. Hopefully it's something easy and I'm just being blind.
Shell: Select all
stderr 2025-02-25 11:42:59 "Setting up watches.
"
stderr 2025-02-25 11:42:59 "Watches established.
"
stdout 2025-02-25 11:43:15 "[INOTIFY] /downloads/The White Lotus S03E02 Special Treatments 1080p MAX WEB-DL DDP5 1 x264-NTb[EZTVx.to].mkv
"
stdout 2025-02-25 11:43:15 "[2025/02/25 11:43:15 UTC] Waiting 300 seconds for changes to settle down...
"
stderr 2025-02-25 11:48:16 "Initialize Cache folder: /data/filebot/cache
"
stderr 2025-02-25 11:48:16 "Initialize Logs folder: /data/filebot/logs
"
stderr 2025-02-25 11:48:16 "Initialize new disk cache: /data/filebot/cache/0
"
stderr 2025-02-25 11:48:17 "Feb 25, 2025 11:48:17 AM java.util.prefs.FileSystemPreferences$1 run
"
stderr 2025-02-25 11:48:17 "INFO: Created user preferences directory.
"
stdout 2025-02-25 11:48:20 "Run script [fn:amc] at [Tue Feb 25 11:48:20 UTC 2025]
"
stdout 2025-02-25 11:48:20 "Parameter: excludeList = .excludes
"
stdout 2025-02-25 11:48:20 "Parameter: unsorted = y
"
stdout 2025-02-25 11:48:20 "Parameter: music = y
"
stdout 2025-02-25 11:48:20 "Parameter: artwork = y
"
stdout 2025-02-25 11:48:20 "Argument[0]: /downloads
"
stdout 2025-02-25 11:48:21 "Failed to read excludes: /media/.excludes: /media/.excludes
"
stdout 2025-02-25 11:48:21 "Abort (×_×)
"
Re: Docker issue with excludes
Posted: 25 Feb 2025, 13:24
by rednoah
Does the user have read / write permissions to this file path?
Code: Select all
Failed to read excludes: /media/.excludes
What does
ls -la say?
What does
touch say?
Shell: Select all
touch /Volume1/Plex/Media/.excludes
Unrelated to the above, your application data folder is
not persistent:
How do I activate my license?
tl;dr This part is important and must not omitted:
yml: Select all
volumes:
- data:/data
Unrelated to the above, your bind mounts are bad:
Notes on --action MOVE and --action HARDLINK
tl;dr This part should look like this:
yml: Select all
volumes:
- data:/data
- /Volume1/Plex:/Volume1/Plex
Re: Docker issue with excludes
Posted: 25 Feb 2025, 14:24
by HarveyBirdman
I think it has permissions, ls -la shows this:
Shell: Select all
drwxrwxrwx+ 1 TimeMachine TimeMachine 60 Feb 10 14:31 .
drwxrwx---+ 1 plex admin 140 Feb 25 11:43 ..
-rwxrwx---+ 1 matheson matheson 0 Jan 30 10:00 amc.txt
-rw-rw-rw-+ 1 matheson matheson 0 Feb 25 14:05 .excludes
drwxrwxrwx+ 1 matheson matheson 8046 Feb 16 21:53 Movies
drwxrwxrwx+ 1 matheson matheson 1010 Feb 19 22:42 'TV Shows'
touch doesn't seem to show anything.
Have added data:/data and changed the Volume mount as recommended thanks.
Re: Docker issue with excludes
Posted: 25 Feb 2025, 15:52
by rednoah
Can you confirm that
matheson:matheson is
1000:1000?
Code: Select all
-rw-rw-rw-+ 1 matheson matheson 0 Feb 25 14:05 .excludes
Run
id to check the current user permissions.
Is the Group ID really 1000?
(NOTE: non-system Group IDs usually start around 100 on typical Linux devices)
Why not run as
plex:admin? Because that seems to be the owner of your
/Volume1/Plex folder.
Note that
+ indicates that there are ACLs. An ACL rule can supersede the
-rw-rw-rw- base permissions. The
filebot process is unable to read that file for some reason, even though it exists and has
r permissions. You can disable the exclude list / specify a different one, but you'd likely run into the same permission issue at a later step, so best to figure it out here.
What is your NAS model / OS platform?
Re: Docker issue with excludes
Posted: 25 Feb 2025, 16:08
by HarveyBirdman
Brill thanks, it's a Terramaster NAS - F4-424 Pro running TOS 5.1.145
The user and group ID appears to be 0
Shell: Select all
uid=0(matheson) gid=0(matheson) groups=0(matheson),3(admin),4(allusers),6(media)
Very new to it so working it out as I go but have got Docker working with a couple of other apps.
Re: Docker issue with excludes
Posted: 25 Feb 2025, 16:53
by rednoah
The
UID / GID that
filebot is running as needs to make sense, otherwise you'll get permission issues while the container is running because of insufficient permissions, or when you then try to access the files later because the permissions are bad:
yml: Select all
environment:
- PUID=1000
- PGID=1000
suggests that everything is running as
root. I guess the
filebot process inside the container will need to run as
root as well then.
User #0 not being named
root is pretty unusual though. I have never used a Terramaster NAS so take everything with a grain of salt.
Running as
0 / root is usually not recommend. I'd probably try to figure out what
UID / GID your
plex:admin user has, and then specify that in the docker config file.
Re: [Terramaster NAS permissions] Docker issue with excludes
Posted: 06 Mar 2025, 09:13
by HarveyBirdman
Brill thanks for the help, I tried changing the user but think I had messed up a load of bits while trying to get it work so deleted everything and started from scratch which seems to have got it all running and working as expected now
, I'm assuming I'd broken some permissions in the process before (not surprised as I don't know what I'm doing haha!)
Thanks again!