Docker cannot "see" volume/folders

[RobRoy90]

Greetings all!

I am really struggling in trying to get Tdarr working in Docker on my Synology RS1221RP+ box. I have it installed, and the server can see the node, but where I am stuck is exposing the relevant file shares on the diskstation to the docker container so that Tdarr can start transcoding.

For example, on my unit I have shares at:

/volume1/Movies
/volume1/TV

Both of these shares have video files in them I want to transcode with Tdarr. I think it is very safe to say I don't understand the relationship between the docker file system and the "global" file system of the NAS itself. I have found the variables for the admin account (1032) and admin group (102) and updated those in the properties of the containers, but I am obviously still missing something.

Thanks, I would really appreciate some assistance here.

-Rob

 

[Rusty]

Greetings all!

I am really struggling in trying to get Tdarr working in Docker on my Synology RS1221RP+ box. I have it installed, and the server can see the node, but where I am stuck is exposing the relevant file shares on the diskstation to the docker container so that Tdarr can start transcoding.

For example, on my unit I have shares at:

/volume1/Movies
/volume1/TV

Both of these shares have video files in them I want to transcode with Tdarr. I think it is very safe to say I don't understand the relationship between the docker file system and the "global" file system of the NAS itself. I have found the variables for the admin account (1032) and admin group (102) and updated those in the properties of the containers, but I am obviously still missing something.

Thanks, I would really appreciate some assistance here.

-Rob

Welcome!

Looking at the compose file for it the volume mapping listed as an example is this

-v /media:/media

Meaning you need to map yours like this:

/volume1/Movies:/media

So left side is your local path and right side is the internal container path. You can use “movies” instead of “media” as I doubt it is hard coded to that name.

If it is then just it as the original documentation states.

If you have option to change the name of the internal folder then just make 2 volume mappings

/volume1/Movies:/movies
/volume1/TV:/tv

 

[RobRoy90]

Welcome!

Looking at the compose file for it the volume mapping listed as an example is this

-v /media:/media

Meaning you need to map yours like this:

/volume1/Movies:/media

So left side is your local path and right side is the internal container path. You can use “movies” instead of “media” as I doubt it is hard coded to that name.

If it is then just it as the original documentation states.

If you have option to change the name of the internal folder then just make 2 volume mappings

/volume1/Movies:/movies
/volume1/TV:/tv

Thank you, that definitely helps, but I am new to Docker on Synology, and I am using the Synology UI to adjust the parameters for the container.

How/where do I find the compose file for a container to edit it?

 

[Rusty]

Thank you, that definitely helps, but I am new to Docker on Synology, and I am using the Synology UI to adjust the parameters for the container.

How/where do I find the compose file for a container to edit it?

Stop the container and then select it in the UI. Click the Edit button to change some of the container parameters.

Jump to Volume tab and configure the mappings. Left column is your host side, right column is the internal destination/folder.