Trouble with tdarr in Docker/Portainer

[RobRoy90]

Can someone please help me with a new install of tdarr in docker/portainer on a Synology NAS? I tried making changes to the config file for tdarr, but it still doesn't "see" into my actual movies folder. On my Synology, the Movies folder is at the "root" /Volume1/Movies and is not nested inside a media folder. I also know Linux is case-sensitive, so could it be that because my "Movies" folder is capitalized that is a contributing factor? Here are updated screenshots of where I am in the process at the moment. You can see from the logs that tdarr still is not "looking" in the right spot, and I don't know how to correct that.

 

[Telos]

It seems you mangled your volume mapping. What is your source for docker compose structure?

 

[RobRoy90]

Thanks, I agree it is mangled. The question is, how do I fix it? What I am struggling with is the relationship between a Synology file path and a Docker file path and how to reconcile the two? I know one is relative to the other, and I also believe there could be file permissions issues to account for as well. The docker folder is at the same level in the file system as the folder that contains my movies.

That is why I posted the screenshots I did. Here is the original docker compose string I tried to start with:

version: "3.9"
services:
tdarr:
image: ghcr.io/haveagitgat/tdarr:latest
container_name: Tdarr
hostname: tdarr
security_opt:
- no-new-privileges:true
healthcheck:
test: wget --no-verbose --tries=1 --spider http://localhost:8265/ || exit 1
ports:
- 8265:8265
- 8266:8266
environment:
- TZ=Europe/Bucharest
- PUID=1026
- PGID=100
- serverIP=tdarr
- serverPort=8266
- webUIPort=8265
- internalNode=true
- nodeID=InternalNode
volumes:
- /volume1/docker/tdarr/server:/app/server
- /volume1/docker/tdarr/configs:/app/configs
- /volume1/docker/tdarr/logs:/app/logs
- /volume1/docker/tdarr/media:/media
- /volume1/docker/tdarr/temp:/temp
restart: always

 

[Telos]

volumes:

• /volume1/docker/tdarr/server:/app/server
• /volume1/docker/tdarr/configs:/app/configs
• /volume1/docker/tdarr/logs:/app/logs
• /volume1/docker/tdarr/media:/media
• /volume1/docker/tdarr/temp:/temp

restart: always

That's likely your problem. Never change the path to the right of the colon. That belongs to the image creator.

I didn't check the rest, but the volume designations are definitely munged on your version. Hopefully that will resolve your issue.

 

[dimfil]

It seems that your problem is at the following line :

- /volume1/docker/tdarr/media:/media

The part on the left of the colon should point to the actual folder of your media, which should be /Volume1/Movies in your case.

 - /Volume1/Movies:/media

Also, the user with puid/guid details that you specified must have access to this folder.

 

[one-eyed-king]

That's likely your problem. Never change the path to the right of the colon.

At least not unless you know the impact and how to configure the application inside the container if deviating container paths are used. Never applies if you have no idea how to configure the application to use deviating path

 

[Telos]

Never applies if you have no idea how to configure the application to use deviating path

In my experience, most users having the issues of this thread, fall into that category. But you are correct. I must never use "never"

 

[one-eyed-king]

Actually tdarr looks quite interesting: a distributed transcoder.

I found the official documentation and the /app/* vollume mappings look fine according: Run and Compose | Tdarr

Note: while the docker run examples show hardware transcoding, the compose example lacks an example for hardware accelerated transcoding, but instead shows a tdrr and tdrr_node setup.

[offtopic]
Btw. If anyone is interested, I recently figured out how to run ClusterPlex with a containerized Plex on the NAS + a transcoder node to offload hardware accelerated transcoding
[/offtopic]

 

[Telos]

On my Synology, the Movies folder is at the "root" /Volume1/Movies and is not nested inside a media folder.

Just fyi... This will then mean that tdarr won't see other media you have... for example tv shows, as there is only one media volume mapping (others can correct me).

As I run Plex via Docker, my media files look like this...

/volume1/media
/volume1/media/movies
/volume1/media/tv shows
/volume1/media/ ...

By doing this my mapping would be
/volume1/media:/media

Then, when I create a tdarr library, I can choose all media forms for transcoding...

Since by far and away, tv shows account for the greatest storage on my system, I would want to include them with tdarr.

 

[RobRoy90]

I understand your point about not having all my types (TV, etc) nested under "media" but right now, Movies are my focus. In light of that, I updated the configuration as attached but it still does not see my Movies library and I am very confused and quite frustrated. Thanks for your patience with me, I know it is something simple and once it clicks, I will be good. Just not there yet. Also, if you stop a stack from running, make changes to the configuration in web editor, and then restart the stack, it re-reads the config file on each restart, correct? Also, I checked the PUID/PGID and made sure it was right for my system.

 

[Telos]

I've not run tdarr in docker, so my comments may not be precise... but when I see this

I've got to wonder whether the path should be:

/media (the container path), or
/volume1/Movies

I suspect /media is correct. Then "scan".

 

[dimfil]

I understand your point about not having all my types (TV, etc) nested under "media" but right now, Movies are my focus. In light of that, I updated the configuration as attached but it still does not see my Movies library and I am very confused and quite frustrated. Thanks for your patience with me, I know it is something simple and once it clicks, I will be good. Just not there yet. Also, if you stop a stack from running, make changes to the configuration in web editor, and then restart the stack, it re-reads the config file on each restart, correct?

No, you have to update the stack choosing the "update the stack" button at the stack editor window. Only then the stack is updated with the changes you made on the editor. You don't have to stop the stack, when you update (redeploy) the changes are applied on the fly.

Also, I checked the PUID/PGID and made sure it was right for my system.

The numbers maybe correct, but for sure double-check the permissions. If you have created a special user for docker usage (that is a good practice to follow) then this user should have permissions to your movie folder. Double-check that on DSM control panel --> User & Group