More > JRiver Media Center 22 for Linux

[NEW] Docker image - MC headless server

<< < (3/6) > >>

Flyingsparks:
Hi Cassfras,
I finally got to try it again last night and it is working again. Many thanks.

JasonAG:
Hi Cassfras,

I'm hoping you can help as I also have a Synology unit (DS1815+) and have been having trouble with this Docker image, specifically related to permissions. I'm not so new to docker, but this is the first time I'm venturing outside those that are created by linuxserver.io.

Anyways, after creating the data container, I can successfully create and run the app container with the code:


--- Code: ---docker run -d --name=jrivermc22-latest --net=host --pid=host -e UPDATE=no -e VNCPASS=jriver --volumes-from jrivermc22--data-container -v /volume1/music:/mnt/media cassfras21/jrivermc:latest
--- End code ---

(as you can guess, all my music is in a "music" shared folder; both the administrators and users groups have read/write access)

I can log in through VNC, but once I browse to /mnt/media, I get the dialog "Could not read the contents of media: Permission denied."

I've tried the following, but with no success:

* Executing the container with high privileges
* Creating a jriver user/group on the synology with read/write access to Music
* Passing in PUID/PGID environment variables, much like the LinuxServer.io containersAt this point, I don't know what to do next, but I really want for this to work. Any ideas?

cassfras21:
Hi Jason,

I think this is more a permission restriction on your Synology folder /volume1/music

Does public have r/w access on /volume1/music folder?

On my Syno I have the following permissions


--- Code: ---drwxrwxrwx   1 root            root            2.0K Feb  5 10:30 music

--- End code ---

JasonAG:
Cassfras,

This is the craziest thing. The other night I SSH'ed in and checked permissions, and they looked like this:


--- Code: ---drwx------   1 root            root             1406 Mar 27 19:59 music
--- End code ---

Not sure if it was because I've been adjusting some File Service / Service discovery settings, but I just checked, and now it looks like this:


--- Code: ---drwxrwxrwx+   1 root            root            1406 Mar 27 19:59 music
--- End code ---

Looks like it has propagated to all subdirectories and files too. I'm assuming it should work now. Strange, but I'll take it?

cassfras21:
Jason,

Look the symbol + in your folder permissions drwxrwxrwx+. It means you enabled extended permissions support for NTFS on your music folder. It's disabled by default. It explains why your permissions changed.

I assume it should work as intended now.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version