Giters

jlesage / docker-avidemux

Docker container for Avidemux

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Using Synology NAS, cannot see sub-folders and files

CTJohnK opened this issue · comments

commented

I'm new to Docker, so perhaps I have misconfigured something, but I access Avidemux and try to open sub-folders or files, nothing appears in the UI dialog.

I have the system configured -

User: '1000' with r/w access to the share
Group: 1000 with r/w access to the share

Added Folder mapping from share to '/storage/recordings'

Explicitly set Local Ports to Container Ports.

  • tried changing 'USER_ID' and 'GROUP_ID' to existing users and groups
  • tried changing 'APP_USER' as default 'app' to '1000' or an existing user

Can see 'recordings' folder under 'storage' in UI, but no sub-folders or files appear.

Any idea what I have missed?

Thank you for your help in advance.

commented

Looks like a permission issue... Can you double check (with ls -l /path) in a terminal that your share has proper ownership/permissions ?

commented

ls -l /storage/recordings returns the screenshot.
I have user 1000 and group 1000 having read/write access to the original mapped folder.

Screenshot_20201230-224450

commented

Hopefully this set of screenshots makes better sense -
This is the revised volume mapping to the 'root' multimedia share:
Capture

Here is the user 1000 config:
Capture5

Capture6

1000 Group setting:
Capture7

"ls -l /storage" (interesting note, the old mapping directly to 'recordings' still appears even though it was removed from the volume mapping)
Capture1

"ls -l /storage/multimedia" (/multimedia is the 'root' of the share and the user 1000 and group 1000 have R/W access to 'multimedia')
Capture2

"ls -l /storage/multimedia/recordings"
Capture3

"ls -l /storage/multimedia/recordings/tv"
Capture4

What Avidemux shows in Folders:
Initial folder screen:
Capture8

Drilling into 'storage':
Capture9

Drilling into 'storage/multimedia':
CaptureA

commented

Two other notes, this behavior occurs with Chrome, Firefox or VNC. Also, I realized I needed to 'Clear' the container to remove the old mapping, this was done and 'recordings' is no longer present. I guess it helps to re-read the manual. :-)

commented

The multimedia folder is owned by root/root and there is permission on it...

Also, from what I understand, the user 1000 is the name of the user, not its numerical id. To remove confusion, I would suggest that you use a real name, like cont_app or something like that. Then use https://github.com/jlesage/docker-avidemux#usergroup-ids to find out its numerical ids and use them in USER_ID and GROUP_ID environment variables of the container.

commented

This seems to be the issue. When I run the 'ID' command ('id 1000', 'id admin' or 'id root') only 'id root' returns a value, the others return "id: unknown user admin" as an example for 'id admin'".

I'd rather not run the container with the 'root' user ID of '0', but I cannot get the container to report any other UID.

Thank you for your response and I hope you're enjoying the holidays.

commented

Did you try to rename your user ?

commented

Ok, I figured this out. Turns out I should not execute the 'ID' command from the container's Terminal session available in Synology's DSM. I needed to actually SSH into the NAS to get the ID.

'Fun fact' if I set the Environment up with USER_ID = 1000, GROUP_ID = 1000 and APP_USER = app, the Terminal command from within the Container (id app) returned '1000' for the user and group. If I changed the USER_ID and GROUP_ID to 1024, cleared, restarted and ran 'id app' again, it returned '1024' for both.

So, I SSHed into the NAS and ran 'id app' and got a uid of 1035 and gid of 100. Plugged those into the Environment variables and changed user name '1000' to 'app' - I'm able to get in.

Thank you for your help, sorry I was a bit 'slow'.