Topic: Docker image with MC25 (Read 8733 times)

Jatzoo · « **on:** April 01, 2019, 02:24:16 pm »

If someone needs it, I created a docker image with new JRiver Media Center (based on the solution by cassfras21/jrivermc).

Headless server only (doesn't support audio/video local rendering)
DLNA is supported (server and controller only)
Using "Latest" repository

Link: https://hub.docker.com/r/jatzoo/jrivermc25

Scobie · « **Reply #1 on:** April 01, 2019, 05:32:26 pm »

Excellent thank you Jatzoo.

rycher · « **Reply #2 on:** April 02, 2019, 11:46:06 am »

Hi,
I'm not an expert. After I installed everything I try to enter JRiver Panel but I don't know what data I need to enter in the Login? What should I write? Thanks for the reply.

Best Regar

Rycher

JimH · « **Reply #3 on:** April 02, 2019, 01:33:35 pm »

Did you set Authentication on the server (MC)? That's the login and Password that Panel uses.

rycher · « **Reply #4 on:** April 02, 2019, 03:11:29 pm »

Hi JimH,
I believe I didn't understand anything, sorry. I installed jriver Docker in ContainerStation in my Qnap. I bought the JRiver license for Linux. I put the registration code but will not accept it. You ask me if I put authentication on the MC server, but where? Have patience, this is my first experience. Thanks for the reply.
Best regards

rycher · « **Reply #5 on:** April 02, 2019, 03:17:50 pm »

Is the MC server located in the Jatzoo file? Or do I have to install it separately? Where is it? Excuse my ignorance .....
Now I listen to music using MC22 installed in HDstation. I wanted to try to install MC25 ..... but I don't understand how it works. I thought it all worked through Docker.

Scobie · « **Reply #6 on:** April 02, 2019, 05:09:09 pm »

Hi Rycher.

Yes everything is located in the container file but you need to do some post setup in MC itself.

You should be able to access the MC UI using VNC with the default password of jriver.

Once in there set up the authentication for panel and all your other options.

The Docker image will work for 30 days as per a standard trial, so you should license it in the UI by the standard method.

rycher · « **Reply #7 on:** April 02, 2019, 05:19:01 pm »

Hi Scobie,
Thanks for the reply. How to use VNC? How do I install it?

Scobie · « **Reply #8 on:** April 02, 2019, 05:27:53 pm »

VNC is client / server remote access software. Jatzoo has a VNC server built in to the Docker image so you need a VNC client.

VNC clients are freely available so have a hunt around for the type you need, Linux or windows, I use RealVNC for Windows.

You can also setup VNC access from a browser, I believe Chrome has a plugin.

rycher · « **Reply #9 on:** April 02, 2019, 06:16:13 pm »

Hi Scobie,
Is it okay even Putty? Once I have installed a VNC client what should I do? Sorry but I never used it. I do not know how to use it. I use Ubuntu as an operating system. Thank you

Scobie · « **Reply #10 on:** April 02, 2019, 06:50:04 pm »

Hi Rycher.

Sorry but I'm not sure whether putty or xserver will do the job here, getting to the fringes of my linux knowledge, but sounds like you need to download and install VNC Viewer (what I have been calling the client).

https://www.realvnc.com/en/connect/download/viewer/linux/

When you launch the client, point it to the IP address of the MC server and authenticate with the password jriver. This will enable remote access to the Docker MC25 image.

rycher · « **Reply #11 on:** April 03, 2019, 04:03:40 am »

Hi Scobie,
I installed VNC, started ContainerStation, opened the JRiver Panel web page, entered the IP address of the page on VNC and gave me this error: The connection closed unexpectedly. I tried to enter the IP of the Qnap but no page opens. I can't go on. I thank you for your availability. I'm really denied for these things.
Rycher

Scobie · « **Reply #12 on:** April 03, 2019, 04:03:37 pm »

Hi Rycher, you need to enter the IP of the Docker image which may be different to that of the QNAP. How did you set up networking?

It might help to look at Jatzoo’s instructions for the installation of is MC24 Docker image, they are still good for MC25.

https://yabb.jriver.com/interact/index.php/topic,115841.0.html

rycher · « **Reply #13 on:** April 04, 2019, 08:35:55 am »

Hi Scobie,
thanks for the advice. I try to do as you say. I hope to be able to execute the exact settings.
Best Regards
Rycher

Scobie · « **Reply #14 on:** April 14, 2019, 11:17:06 pm »

Jatzoo am i able to point my Docker Image to a different repository?

Jatzoo · « **Reply #15 on:** April 16, 2019, 01:38:44 am »

You can try to login to container via SSH, uninstall MC (or try with what it is) and change repo with this tutorial: https://yabb.jriver.com/interact/index.php/topic,119969.0.html.
But I do not know that MC will survive this and will work.

Scobie · « **Reply #16 on:** April 16, 2019, 08:04:25 pm »

Thanks Jatzoo will give that a try.

But just for my own curiosity (trying to get my head around Docker containers) where/how in the current setup is the config to update by accessing the "latest" repository?

Cheers

Jatzoo · « **Reply #17 on:** April 17, 2019, 03:28:51 am »

I define repository in dockerfile before create image. You can see example here: https://hub.docker.com/r/cassfras21/jrivermc/dockerfile (find: #Add JRiver packages to apt-get).

Scobie · « **Reply #18 on:** April 17, 2019, 04:54:53 am »

Ah ok I see now.

So could I simply edit that code to point to a different repository and create a new image?

Jatzoo · « **Reply #19 on:** April 17, 2019, 05:08:14 am »

Yes, but You must use another few files to create image. See here: https://github.com/cassfras21/docker-jrivermc/tree/master/stable.

Scobie · « **Reply #20 on:** April 17, 2019, 07:36:09 am »

Thanks again Jatzoo

Scobie · « **Reply #21 on:** April 30, 2019, 01:05:10 am »

Quote

You can try to login to container via SSH, uninstall MC (or try with what it is) and change repo with this tutorial: https://yabb.jriver.com/interact/index.php/topic,119969.0.html.
But I do not know that MC will survive this and will work.

FYI this worked well. I simply accessed the container through the built in terminal interface and updated the relevant list.d file to point to the beta repo.

On next update request it installed the beta over the existing install without error.

Thanks again (again).

Jatzoo · « **Reply #22 on:** May 01, 2019, 11:01:06 am »

Scobie, I'm glad it worked

NoFace · « **Reply #23 on:** July 13, 2019, 06:02:46 am »

Amazing work. Thanks Jatzoo

ajw1997 · « **Reply #24 on:** July 18, 2019, 07:21:32 am »

Hello,
I'm running the docker version on my QNAP NAS within Container Station.
Whenever I need to update the OS on my NAS and re-start it, the container also needs to re-start.
Which means I need to re-enter my licence key.
I have now zero restores left!

So is there a way to change the docker configuration to avoid having to re-enter the licence key all the time using up restores?

Regards,

Andrew

bob · « **Reply #25 on:** July 19, 2019, 04:09:06 pm »

Quote from: ajw1997 on July 18, 2019, 07:21:32 am

Hello,
I'm running the docker version on my QNAP NAS within Container Station.
Whenever I need to update the OS on my NAS and re-start it, the container also needs to re-start.
Which means I need to re-enter my licence key.
I have now zero restores left!

So is there a way to change the docker configuration to avoid having to re-enter the licence key all the time using up restores?

Regards,

Andrew

Send an email to bob (at) jriver (dot) com and I'll reset your restores.

Scobie · « **Reply #26 on:** July 22, 2019, 06:47:21 pm »

Quote

So is there a way to change the docker configuration to avoid having to re-enter the licence key all the time using up restores?

I had the same issue and asked Jatzoo a while back.

The solution is to create a data volume for persisting container data. This is a specifically designated directory that directly interacts with the host file system, and is required for maintaining data generated by the containers

I have never actually tried this but it should work. This is Jatzoo's response to my query:

Quote

Scobie, if You want to test, please delete current container with JRiverMC and create again with my step-by-step instructions from previous page with small change - in step 6 for "Mount Point": "/home/jriver/.jriver" please enter in "New volume": "jrivermc_data" - this will create a persistent volume for JRiverMC data (You will be able to see it in menu Volume in Container Station)

ajw1997 · « **Reply #27 on:** July 22, 2019, 09:11:38 pm »

Thanks.
I will give this a go.
But before I do, I will need to figure out how to save/backup my library from within Docker, so that I reuse it later!

Scobie · « **Reply #28 on:** July 22, 2019, 11:01:22 pm »

Just back it up to the shared volume your media files are on.

ajw1997 · « **Reply #29 on:** July 26, 2019, 11:10:10 pm »

Hi,
I'm having problems with the dockerised version of JRiver 25 freezing when I try to add new files.
This has only occurred in the last day or so...after an update.

To see if this could be a problem with the new JRiver version 83, how do I edit the container to not use the 'latest' version.

But rather the 'stable' version of JRiver.

Regards,

Andrew

max096 · « **Reply #30 on:** July 27, 2019, 12:29:25 pm »

Quote from: ajw1997 on July 26, 2019, 11:10:10 pm

Hi,
I'm having problems with the dockerised version of JRiver 25 freezing when I try to add new files.
This has only occurred in the last day or so...after an update.

To see if this could be a problem with the new JRiver version 83, how do I edit the container to not use the 'latest' version.

But rather the 'stable' version of JRiver.

Regards,

Andrew

https://hub.docker.com/r/jatzoo/jrivermc25/tags

Jatzoos image only is built once and updates on start. The image was built several months ago. If you create a new image and set update to NO you will have a version that's quite a lot older to test with.

max096 · « **Reply #31 on:** July 27, 2019, 04:49:14 pm »

What you can do to get back to stable is create a file "mediacenter25.list"

with this inside

Code: [Select]

#MC
deb [arch=amd64,i386,armhf] http://dist.jriver.com/stable/mediacenter/ jessie main

Then you mount the file as a volume to "/etc/apt/sources.list.d/mediacenter25.list" set the UPDATE to yes. Now whenever the container updates it should get the version from the stable repository. The change should persist. No ssh into the container on every reboot required.

Although, you will have to delete the container and recreate it once. (or ssh into it and reinstall jriver) Because it won't be updating to an older version of MC if you got one installed that's newer.
As long as you map your .jriver directory into it again. You should be fine.

I'd be very surprised if that fixes that though. Latest so far has been very stable and we have seen latest and stable repositories be at the same version. So I do not want to believe they would be breaking basic functionality, such as importing new files. But maybe it somehow plays out that way with that image.

ajw1997 · « **Reply #32 on:** July 27, 2019, 06:30:25 pm »

Hello,
Thanks for this.
Yes, I'd rather try and get the jatzoo container to work again, rather than try something completely different.
So try to make it the stable version.
A question.
I've created the file you specify (in Notepad).
Where do I save it, and how do I tell the Container Station where to get it from?

I'm only guessing that the new JRiver version is the cause of my problems, as nothing else has changed in my settings.

Regards,

Andrew

ajw1997 · « **Reply #33 on:** July 28, 2019, 12:44:53 am »

Hello,
I managed to:

reinstall the container, changing the update setting to NO
running the JRiver version within the original container (version 15 from memory)
SSH into the container, and installed the stable version of JRiver for Linux (version 50).

In both step 2 and 3, the problem recurs.
When I manually try to import a new folder, nothing happens.
I can move the mouse. But nothing else can be done.
I thought it may be a JRiver version problem, but that can't be the case.

Is anyone else having this problem using the Jatzoo docker container?

Regards,

Andrew

max096 · « **Reply #34 on:** July 28, 2019, 07:44:41 am »

Quote from: ajw1997 on July 27, 2019, 06:30:25 pm

Hello,
Thanks for this.
Yes, I'd rather try and get the jatzoo container to work again, rather than try something completely different.
So try to make it the stable version.
A question.
I've created the file you specify (in Notepad).
Where do I save it, and how do I tell the Container Station where to get it from?

I'm only guessing that the new JRiver version is the cause of my problems, as nothing else has changed in my settings.

Regards,

Andrew

It does not matter where you save it. It only matters that you map it to the right path within the container. Similarly to how you got your music directory into the container, but in this case only 1 file no directory.

ajw1997 · « **Reply #35 on:** July 29, 2019, 05:20:38 pm »

Hello,
The problem of JRiver freezing when I manually add new folders seems to have resolved itself.
I had set it to automatically import new folders. When it also froze.
But when I came back later to use JRiver it seems to have imported new folders.
And the 'manually add new folders' seems to be working again.
Bizarre!

Regards,

Andrew

max096 · « **Reply #36 on:** July 30, 2019, 03:47:42 pm »

Quote from: ajw1997 on July 29, 2019, 05:20:38 pm

Hello,
The problem of JRiver freezing when I manually add new folders seems to have resolved itself.
I had set it to automatically import new folders. When it also froze.
But when I came back later to use JRiver it seems to have imported new folders.
And the 'manually add new folders' seems to be working again.
Bizarre!

Regards,

Andrew

Thats good then. Maybe you restarted the NAS or the 'container station' thing? Ive had docker die inside a few times already immidiately after an upgrade of docker itself. Restarting the service always fixed it again. But I dont know how to do that on what you are using. Restarting the entier system is the surefire way to achieve that though. Guess it just does not like it being replaced while its running.

Should add that to my list of remembering people to ask if they tried 'turning it off and on again'. It sounds kinda crishy, but it just works so often.

ajw1997 · « **Reply #37 on:** August 09, 2019, 05:49:28 pm »

Hello,
After using Jriver25 with docker for a month or so, it is now not installing.
When trying to run it I get the message:

E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?

My reading of Google search results is that the 'image' needs to be revised to install the relevant package.
Is that correct?
If yes, how is this done?

Regards,

Andrew

max096 · « **Reply #38 on:** August 10, 2019, 11:53:10 am »

Quote from: ajw1997 on August 09, 2019, 05:49:28 pm

Hello,
After using Jriver25 with docker for a month or so, it is now not installing.
When trying to run it I get the message:

E: The method driver /usr/lib/apt/methods/https could not be found.
N: Is the package apt-transport-https installed?

My reading of Google search results is that the 'image' needs to be revised to install the relevant package.
Is that correct?
If yes, how is this done?

Regards,

Andrew

What does it say when you run the image without the -d option or look into "docker logs image_name_or_id" when it "runs".
The image should not need any rebuilding to work.

Have you tried removing the container and recreating it? Or does it work when you create a new container entirely from scratch?

You could always "docker exec -it <container_name> /bin/bash" and then "apt intall apt-transport-https" (as a test if it works then), but normally it should not be needed. It works without that package. apt-transport-https was never installed in that image.

ajw1997 · « **Reply #39 on:** August 10, 2019, 06:18:23 pm »

Hello,
Thanks for your response. This asks great questions.

Before I respond, here is a copy of the log from the file "*-json.log"

{"log":"\r\r0% [Working]\r \rE: The method driver /usr/lib/apt/methods/https could not be found.\r\n","stream":"stdout","time":"2019-08-10T23:04:50.849676925Z"}
{"log":"N: Is the package apt-transport-https installed?\r\n","stream":"stdout","time":"2019-08-10T23:04:50.84982343Z"}

I respond to your questions below.

Q1. What does it say when you run the image without the -d option or look into "docker logs image_name_or_id" when it "runs".
The image should not need any rebuilding to work.

Answer:
I can see no "-d" option. I installed the docker using the Jatzoo instructions for JRiver 24.
Where would the "docker logs image_name_or_id" be?

Q2. Have you tried removing the container and recreating it? Or does it work when you create a new container entirely from scratch?

Answer: I have tried that multiple times, but as mentioned, using the Jatzoo instructions.

Q3. You could always "docker exec -it <container_name> /bin/bash" and then "apt intall apt-transport-https" (as a test if it works then), but normally it should not be needed. It works without that package. apt-transport-https was never installed in that image.

Answer: As the container does not actually run, I don't believe this is possible.

My Theory
Based on this post https://stackoverflow.com/questions/55834331/docker-image-rabbitmq-apt-broke, could it be that the container is trying to install/download a no longer maintained Linux respository?

If this is the case, the image may need to be updated.

Regards,

Andrew

max096 · « **Reply #40 on:** August 11, 2019, 06:44:00 am »

Restarting docker or the entire PC sometimes helps with weird docker problems.
I dont think your theory is right since jatzoo's image does work for me (I'm not actually using it, I just tried if it works yesterday). But I don't know right now how to possibly remote troubleshoot that.

You could try to "docker rm -f <your_container>", then "docker image prune" to remove un-used images. Then try "docker run" again. Could be that the image somehow currupted on your PC. Although, I have never encountered it.

Either way the apt installation in jatzoos image is not broken and the image was never changed or updated since it was uploaded, since the way it updates is with apt inside the container. I can confirm is working as of yesterday.

-------------------------------------

But

https://hub.docker.com/r/shiomax/jrivermc25

You could try this one.

For that create a new directory "config" then move your current directory into that directory and name it ".jriver". (As always better first backup your current directory).

Then you can use this run command

Code: [Select]

docker run -d \
    --name=jrivermc25 \
    --net=host \
    --restart=always \
    -v config:/config:rw \
    -v /path/to/music:/data/music:rw \
    -e VNC_PASSWORD=12345 \
    shiomax/jrivermc25

You should also replace "/data/music" with the path where you stored your music in the other container in the other image and the "path/to/music" with your music directory on the host. For the config directory this command assumes you are running the command from the directory where the config directory is located on your disk. If you run it from anywhere else you can, but you will have to provide the full path to it then.

This image never should have problems with apt, since it does not have apt installed and does not update at runtime. Updates are handled entirely at build time and its currently automatically rebuilding every Sunday. If a new image that was built causes problems you can use one of the previously built image. You can find more information about that in the readme.

To update that image with the docker commands. You can run these three commands (replace the last command with whatever you ran before when initially creating the container)

Code: [Select]

docker pull shiomax/jrivermc25:latest

docker rm -f jrivermc25

docker run -d \
    --name=jrivermc25 \
    --net=host \
    --restart=always \
    -v config:/config:rw \
    -v /path/to/music:/data/music:rw \
    -e VNC_PASSWORD=12345 \
    shiomax/jrivermc25

Or you use compose as suggested in the readme. Then you don't have to keep track of the run command somehow.

ajw1997 · « **Reply #41 on:** August 14, 2019, 04:49:22 am »

Hello,
After much digging, it seems that the problem with how my QNAP NAS accesses the internet.
It was not able to update the virus definitions, and other issues.
Anyway, I found a post about this problem, with the advice to change the DNS settings to 8.8.8.8 and 8.8.4.4.
https://forum.qnap.com/viewtopic.php?f=25&t=144837
And it now all works again fine.
I'm not sure what the problem was-may have been from a QNAP OS update. Anyway it now works.
Thanks for trying to help.
Bizarre.
Regards,
Andrew

Grundgütigster · « **Reply #42 on:** September 13, 2019, 02:47:22 am »

In my next life I will become a computer expert and be able to install the docker version of MC on my QNAP NAS.

INTERACT FORUM

Author Topic: Docker image with MC25 (Read 8733 times)