Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[cassfras21]

Hello,

I finished my new docker image for JRiver Media Center 22. This is the continuation of my first project.
https://yabb.jriver.com/interact/index.php/topic,106118.0.html

It is now compliant with the last changes in MC so it can be updated to the latest MC version. I used Bob's first method with the xdummy-server to make it work with the new requirements.
https://yabb.jriver.com/interact/index.php/topic,109419.0.html

I added an image for the MC stable repository so now you have the choice to run cassfras21/jrivermc:latest or cassfras21/jrivermc:stable

Everything you need to know to run Docker images is here:
https://hub.docker.com/r/cassfras21/jrivermc/

Learn more and get the source code on my github:
https://github.com/cassfras21/docker-jrivermc

Enjoy

[JimH]

Thanks for your work, and thanks for sharing it.

[stevemac]

Thanks for this.  Will be upgrading to FreeNas10 in the next few weeks and am keen to try out Docker

[Flyingsparks]

Cassfras, I am having issues with your latest version, I cannot seem to be able to log in through VNC.
I think it relates to the changes where you use xserver-xorg-video-dummy. I remember this when creating my original docker container (I have since been using yours )
Rolling back to my old docker container which is using xvfb and openbox, this still works.
I am running docker on Ubuntu 16.04

[cassfras21]

Cassfras, I am having issues with your latest version, I cannot seem to be able to log in through VNC.

Hello,

Can you verify your container's logs in docker and check if vnc starts succesfully?

Mine looks like this. I don't know why but sometimes x11vnc failed on its first start and then it keeps running on its second start.
In any cases I am able to logon to vnc without any issue.

Code: [Select]

2017-03-25 04:23:28 stdout 2017-03-25 04:23:28,988 INFO success: x11vnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-25 04:23:27 stdout 2017-03-25 04:23:27,885 INFO success: mediacenter entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-25 04:23:27 stdout 2017-03-25 04:23:27,884 INFO spawned: 'x11vnc' with pid 26
2017-03-25 04:23:27 stdout 2017-03-25 04:23:27,881 INFO success: Xorg entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-25 04:23:26 stdout 2017-03-25 04:23:26,836 INFO exited: x11vnc (exit status 1; not expected)
2017-03-25 04:23:26 stdout 2017-03-25 04:23:26,808 INFO spawned: 'mediacenter' with pid 14
2017-03-25 04:23:26 stdout 2017-03-25 04:23:26,804 INFO spawned: 'x11vnc' with pid 13
2017-03-25 04:23:26 stdout 2017-03-25 04:23:26,801 INFO spawned: 'Xorg' with pid 12
2017-03-25 04:23:25 stdout 2017-03-25 04:23:25,798 INFO supervisord started with pid 1
2017-03-25 04:23:25 stdout 2017-03-25 04:23:25,769 CRIT Set uid to user 999
2017-03-25 04:23:25 stderr stored passwd in file: /home/jriver/.vnc/passwd

[Flyingsparks]

Hi Cassfras,

It seems the data container is coming up, bu the main container is not. This is using jriver-stable:

Code: [Select]

stored passwd in file: /home/jriver/.vnc/passwd
2017-03-26 06:29:44,074 CRIT Set uid to user 999
2017-03-26 06:29:44,076 INFO supervisord started with pid 15308
2017-03-26 06:29:45,078 INFO spawned: 'Xorg' with pid 15579
2017-03-26 06:29:45,078 INFO spawned: 'x11vnc' with pid 15580
2017-03-26 06:29:45,079 INFO spawned: 'mediacenter' with pid 15581
2017-03-26 06:29:45,081 INFO exited: Xorg (exit status 1; not expected)
2017-03-26 06:29:45,084 INFO exited: x11vnc (exit status 1; not expected)
2017-03-26 06:29:45,116 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:46,118 INFO spawned: 'Xorg' with pid 15582
2017-03-26 06:29:46,119 INFO spawned: 'x11vnc' with pid 15583
2017-03-26 06:29:46,120 INFO spawned: 'mediacenter' with pid 15584
2017-03-26 06:29:46,122 INFO exited: Xorg (exit status 1; not expected)
2017-03-26 06:29:46,125 INFO exited: x11vnc (exit status 1; not expected)
2017-03-26 06:29:46,158 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:48,161 INFO spawned: 'Xorg' with pid 15601
2017-03-26 06:29:48,161 INFO spawned: 'x11vnc' with pid 15602
2017-03-26 06:29:48,162 INFO spawned: 'mediacenter' with pid 15603
2017-03-26 06:29:48,164 INFO exited: Xorg (exit status 1; not expected)
2017-03-26 06:29:48,169 INFO exited: x11vnc (exit status 1; not expected)
2017-03-26 06:29:49,201 INFO success: mediacenter entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-26 06:29:49,201 INFO exited: mediacenter (exit status 0; expected)
2017-03-26 06:29:50,203 INFO spawned: 'mediacenter' with pid 15605
2017-03-26 06:29:50,243 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:51,245 INFO spawned: 'Xorg' with pid 15606
2017-03-26 06:29:51,246 INFO spawned: 'x11vnc' with pid 15607
2017-03-26 06:29:51,246 INFO spawned: 'mediacenter' with pid 15608
2017-03-26 06:29:51,250 INFO exited: Xorg (exit status 1; not expected)
2017-03-26 06:29:51,251 INFO gave up: Xorg entered FATAL state, too many start retries too quickly
2017-03-26 06:29:51,252 INFO exited: x11vnc (exit status 1; not expected)
2017-03-26 06:29:51,281 INFO gave up: x11vnc entered FATAL state, too many start retries too quickly
2017-03-26 06:29:52,283 INFO success: mediacenter entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2017-03-26 06:29:52,283 INFO exited: mediacenter (exit status 0; expected)
2017-03-26 06:29:53,285 INFO spawned: 'mediacenter' with pid 15627
2017-03-26 06:29:53,322 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:54,324 INFO spawned: 'mediacenter' with pid 15637
2017-03-26 06:29:54,361 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:56,364 INFO spawned: 'mediacenter' with pid 15650
2017-03-26 06:29:56,399 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:29:59,403 INFO spawned: 'mediacenter' with pid 15684
2017-03-26 06:29:59,439 INFO exited: mediacenter (exit status 0; not expected)
2017-03-26 06:30:00,440 INFO gave up: mediacenter entered FATAL state, too many start retries too quickly

Any ideas?

[cassfras21]

Yes I have a couple of ideas.

It looks like the problem is coming from Xorg. Maybe it has to do with the fact I run docker on my Syno where there is no video output while you have one display on your computer running Ubuntu.

1) You could try to run the app container without DLNA support

Code: [Select]

docker run -d \
--name=jrivermc22-stable \
-e UPDATE=no \
-e VNCPASS=<vnc_password> \
-h <hostname> \
-p 5900:5900 \
-p 52199:52199 \
--volumes-from jrivermc22--data-container \
-v <local_media_volume>:/mnt/media \
cassfras21/jrivermc:stable
2) Or if you want to find out what's going on, please run the app container with the following command to gain shell access.
It will prevent supervisord from starting.

Code: [Select]

docker run -it \
--name=jrivermc22-test \
--net=host \
--pid=host \
-e UPDATE=no \
-e VNCPASS=<vnc_password> \
--volumes-from jrivermc22--data-container \
-v <local_media_volume>:/mnt/media \
cassfras21/jrivermc:stable \
/bin/bash
Then try to run Xorg manually with the command I copied from the supervisord file and look what happens

Code: [Select]

Xorg :0 -noreset +extension GLX +extension RANDR +extension RENDER
Maybe you should give a try with other display number like this one

Code: [Select]

Xorg :1 -noreset +extension GLX +extension RANDR +extension RENDER

[Flyingsparks]

Yeah, that seems to be the problem. When I try to start with display :0 it doesn't run, but with display :1 it will.

[Flyingsparks]

Here is the actual outputs from Xorg.

Code: [Select]

Xorg :0 -noreset +extension GLX +extension RANDR +extension RENDER
_XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
(EE)
Fatal server error:
(EE) Cannot establish any listening sockets - Make sure an X server isn't already running(EE)
(EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.


Code: [Select]

Xorg :1 -noreset +extension GLX +extension RANDR +extension RENDER
libudev: udev_has_devtmpfs: name_to_handle_at on /dev: Operation not permitted

X.Org X Server 1.16.4
Release Date: 2014-12-20
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.16.0-4-amd64 x86_64 Debian
Current Operating System: Linux Woodstock 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-4.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
Build Date: 11 February 2015  12:32:02AM
xorg-server 2:1.16.4-1 (http://www.debian.org/support)
Current version of pixman: 0.32.6
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.1.log", Time: Sun Mar 26 12:52:11 2017
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"


[cassfras21]

I just built new docker images with a new environment variable MONITOR for both stable and latest repo.
The default value is :1, so in your case the command to run the container is the same as before.

This should fix your issue and allow to run the app container with other screen setup if needed.

[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: [Select]

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
(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 containers

At 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: [Select]

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


[JasonAG]

Cassfras,

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

Code: [Select]

drwx------   1 root            root             1406 Mar 27 19:59 music
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: [Select]

drwxrwxrwx+   1 root            root            1406 Mar 27 19:59 music
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.

[sjhilton]

Hi cassfras21 (and everyone else on this thread),

I'm having an issue with the JRiver docker losing my registration. If I close the container (as opposed to killing JRiver within the container) and restart it then JRiver will come up as being unregistered, which is a bit annoying.

I'm also having trouble registering a media access key - it generates one OK, but if you plug it into JRemote or another client it says it is invalid. A direct local IP connection works fine in JRemote.

I think these issues could be symptomatic of the same network/configuration problem. I'm using the QNAP container station. The container is set up in 'bridge' mode so it has its own IP on the network rather than relying on a private network/port forwarding in the NAS.

I'd be very grateful for any ideas/suggestions. Thanks in advance!

Stuart

[cassfras21]

Hi Stuart,

If I close the container (as opposed to killing JRiver within the container) and restart it then JRiver will come up as being unregistered

I am not able to reproduce this issue on demand. In my case, stoping, force stoping or restarting my container doesn't affect the registration key. But I admit already had this behavior by the past and had to register the licence again. But I can't say how this happens.

Do you run data in a dedicated container as I recommend or are you running everything (app and data) in only one container?

About the media access key issue, this is because your container is set up as bridge instead of host. In fact bridge setup hides you container behind NAT in the docker subnet (172.17.0.0/16). For the same reason DLNA won't work in bridge mode too. Give a try in host mode, but your qnap shouldn't use the same tcp/udp port than your container or it will conflict.

Hope it helps a bit!

[sjhilton]

Hi cassfras21,

Thanks for your suggestions.

I've tried the host mode and it may have solved the registration issue (I just hard reset the container and restarted it then). There doesn't seem to be any port conflicts so that's all fine.

This doesn't seem to have helped with the media access key issue. I have managed to set up port forwarding so I can connect JRemote from the internet now (via IP) and not just the internal network. It's very strange - JRiver doesn't seem to complete the registration or the testing process for the media access key.

I haven't used a separate data container, because I'm not sure how to do that with the QNAP container station (if you have any ideas on this I'd be happy to try them out!) I have managed to backup the data to my media share using the tar instructions you provided.

thanks again,

Stuart

[sjhilton]

Hi cassfras21,

Just thinking perhaps the JRiver registration is linked (in part) to a mac address for the machine? The bridge mode in QNAP container station seems to generate a new mac address every time you stop and start. One of the admins would know if this is likely to be the case.

Stuart

[cassfras21]

Hi Stuart,

It's nice the host mode solved your registration issue. I don't know how the JRiver registration process works but when I met this issue I just need to restore my JRiver data container.

For the separated containers setup I don't have specific instructions for QNAP nor for Synology. To proceed I use docker run commands (these from my Docker Hub page) by connecting to my syno with ssh.

For your media access key issue, did you try to generate a new one since you switched to host mode? Maybe it could help.

[sjhilton]

Hi cassfras21,

Thanks for your reply.

Re the access key - yes I did try to generate a new one and it didn't make any difference. I'm not so fussed about this now as everything seems to work perfectly with a direct IP connection.

I've just done a quick search of the QNAP forum and it looks like it is possible to run docker from the command line using an ssh connection on the QNAP NAS so it should be possible to establish a data only container. I'm sorry if you've posted elsewhere on this, but I was wondering what the main benefits are of having a separate date container? I can backup JRiver data to a tar in my media folder, which seems to work OK and the library is also backed up to the same location - is that enough?

thanks again,

Stuart

[cassfras21]

Hi Stuart,

For a daily use this is not very useful. Purpose it helps for container management. It allows to run multiple containers with the same data container. For example I can run latest JRiver or stable JRiver with the same data container. In case of compromised app container you can rebuild it without the need to restore data or licence.

As long as you are able to save and restore your data even with only one container then it's fine!

[sjhilton]

Thanks cassfras21 - appreciate the guidance. Thanks again for all your work maintaining the 'dockerised' version - it's very useful!

[NoFace]

Is there an update for V23 please 

[Mans]

Greatday,

New to Docker, installed the package today and trying to get JRiver MC as Server running.

After some reading and a couple of tries - Selected 'latest' and can see from the Terminal it's downloading the latest version indeed.
But on each attempt i can notice the following error from the Terminal:
...
Pid 4324.
Terminated by SIGSEGV; not expected.
...
Repeated a couple of times, different pid's.
...
Stop.

Anyone an idea or hint what's been causing this and again i'm not familiar to Docker (yet) :-)

Thanks for your help,

[Jatzoo]

I have the same problem on my Qnap - for me works install two missing libraries:

Code: [Select]

apt-get install libunistring0 libgomp1