Print

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

[brains4eva]

Hi I managed to get an install file for the QNAP hybrid disk station app which is based on MC22 which installed fine.  I have a master licence for JRiver 25 but i tried putting the key in and it say it is for another version.  Would it be possible to get a key that will work on that install?  Would be good to have the JRiver interface straight from the QNAP.  Thanks

[JimH]

MC22 licenses aren't available.  Sorry.

[Scobie]

Would be good to have the JRiver interface straight from the QNAP.  Thanks

Since QNAP pulled the JRiver app, there's been some good work in here on using Docker images in the QNAP Container Station which is the next best thing. There is an MC25 instance that works really well.

[brains4eva]

ah right, i did have a dabble with docker station and MC 24 but not sure if its more because of my lack of knowledge but i didn't get too far with it.  Maybe i'll give it another go...

[Awesome Donkey]

Dockerized MC is really the only option if you want to run MC on a NAS now. Personally, I'd rather just get a Raspberry Pi (or an Id from JRiver) and run MC on that and connect it to the NAS.

[max096]

ah right, i did have a dabble with docker station and MC 24 but not sure if its more because of my lack of knowledge but i didn't get too far with it.  Maybe i'll give it another go...

Since you have a 25 license there are two docker images for it right now. Just look for jrivermc25 on dockerhub. One of them Ive built myself, because I wanted a arguably better one. The other one has been around for years basically.

Ive never used qnaps 'container station'. But im sure we can figure that out if you have any problems with it.

[Scobie]

i did have a dabble with docker station and MC 24 but not sure if its more because of my lack of knowledge but i didn't get too far with it.  Maybe i'll give it another go...

It is actually quite easy to use and does a lot of the config lifting for you. I wrestled with how to employ various Docker settings for a while til I found the QNAP CS applied them for me as part of the image setup.

[max096]

It is actually quite easy to use and does a lot of the config lifting for you. I wrestled with how to employ various Docker settings for a while til I found the QNAP CS applied them for me as part of the image setup.

Its really not that hard to do that with the cli or compose as well. If you know your way around a little bit with the docker cli for many things this qnap gui seems largly unnessesary. It didnt seem to me to really do anything automatically. It just gives you a gui with different labels on things.

Docker container settings are mostly always part of the create process (there are a few exceptions that you can edit). But for the most part there is no 'edit'. There is create and remove. Edit = combine the two. Containers arent supposed to preserve any state by themselves. The way you do that is either by bind/volume mounts or docker data containers witch are largly deprecated and replaced by named volumes.

I'd expect that you'll have more luck this time. Since the 24 image was using data containers and I checked now jatzoos image does not seem use them anymore (the 25 one) and mine never did. With data containers you'd effectively have to create 2 'containers'. With volumes you don't and named volumes are just a way to give a volume a name, so you can refer to it easier when you have to use the same volume in multiple containers.

[Scobie]

I think it was mostly volume access I struggled with until the CS UI pointed to the local NAS volume natively. It was simply my lack of Container knowledge that tripped me up, but the UI helped me out there.

[brains4eva]

ah right yes i see it. i managed to install it and run the container.  It doesn't come up with a URL though.  it says in the console, cannot read file system info for /console/music/ no such file or directory

I tried Yatzoo one too and that one runs and say been running for more than 1 second but no URL to UI on that either...

[Scobie]

The only trap is if using the QNAP GUI, the settings need to be entered on create, you can't change them after (I don't think).

So clobber that instance and import again, and put your network and shared folder settings in as part of the import process. This will let you browse and point to the media share folder you have created on the NAS. (See attachment).

[astromo]

Dockerized MC is really the only option if you want to run MC on a NAS now. Personally, I'd rather just get a Raspberry Pi (or an Id from JRiver) and run MC on that and connect it to the NAS.

I'm with AD on this. Use your NAS for storage, map that location over your network via an Id or your MC application on Win, Linux or OSX and go for gold. I've got MC set up on my Qnap but, honestly, I never use it as a server. I loaded it initially to test things out from a position of general interest and to help out. Each to their own. At least MC Docker gives you a proven option to go down that road if that suits your situation. As long as it works and your happy - enjoy the result.

[brains4eva]

The only trap is if using the QNAP GUI, the settings need to be entered on create, you can't change them after (I don't think).

So clobber that instance and import again, and put your network and shared folder settings in as part of the import process. This will let you browse and point to the media share folder you have created on the NAS. (See attachment).

OK, i've gone to do the import again and gone to shared folders area.  Under folders on host, i think i need to add my music folder?  I can't seem to put anything in the host path box,  It has a drop down which comes up with my NAS name, but i can't seem to select it or type anything...

My other question is would i need an absolute path?  I have the music within the multimedia area which is kind of just there when you set up a qnap...
 I'm thinking perhaps the path might be simply /Multimedia/Music but not sure if that's the whole path...

[Scobie]

You should create a Share, and have that as the same name as the Shared folder you point to within MC for your library.

So I have the same file structure as you, the QNAP has a folder called Multimedia. I share that out on the QNAP as "mediashare" and point to that in my CS setup - see the screenshot in my previous post. I give a JRiver user rights to this folder.

Now if I use the CS terminal to access the bash shell I can see the mediashare folder.

[max096]

ah right yes i see it. i managed to install it and run the container.  It doesn't come up with a URL though.  it says in the console, cannot read file system info for /console/music/ no such file or directory

I tried Yatzoo one too and that one runs and say been running for more than 1 second but no URL to UI on that either...

I'm not sure what you mean with no URL.

Normally, as far as docker is concerned by default you use bridge networking. Witch means docker manages it's own network inside the container. And if you want anything to be accessable from the outisde you have to start mapping ports. I have a section on my gilab that shows what ports JRiver needs (or specifically my container) https://gitlab.shio.at/max/jrivermc25-docker#ports
This is also true for Yatzoo's image, except port 5900 is not a thing. As that image only has VNC access. And no novnc webui.

You can also alternatively use host networking. In witch case you do not have to map ports individualy, but instead it will use the hosts (your NAS network). That is what happens if you select a network in your network tab most likely.

Neither one is better or worse necessarily. Bridge networking gives you more flexibility in that you can forward ports if ports would otherwise collide with each other. Host networking gives you the ability to not do that and just straight up use your host network.

For Yatzoo's image you should also set the environment variable UPDATE to yes. That way it updates to the latest jriver on start. My image does that differentlly. It currently rebuilds the entire image every sunday. So to update the image, you would pull the latest image. The image itself does not even contain a package manager to be able to possibly update by itself. That's one of the reasons it's smaller.

---

As far as directories go ofc you will need to map your music directory into the container, but also more importantly you will need to map your ~/.jriver directory or it will be lost on restart.

For my image you do that by mapping /config to whatever you want and for Yatzoo's image you do that by mapping something to /home/jriver/.jriver. This will make your settings, playlists and license persist. If you do not do this it will be as if you just installed jriver every single time you restart the container.

---

To connect to the container you will need a VNC client, or if you use mine you can use a web browser as well. With VNC you type in your IP address of your NAS and then the port 5800 (unless you changed it) for the webui it's your ip address and port 5900.

---

On a side note ofc I'm a bit biased towards my own image. I didn't make it for fun. I made it because I thought I can do better than what already was there. And I think I did just that just fine at that (at the very least for myself I did). But you can use whatever you want the other image has been around for 3 years or so with very little change. It has been obviously tested a lot longer than mine has.

[max096]

The only trap is if using the QNAP GUI, the settings need to be entered on create, you can't change them after (I don't think).

This is pretty normal, unless qnap added a "edit" gui on top of it that would essentially delete and recreate the thing. You cannot edit most of what makes a docker container. You can change some things, but most of the configuration you cannot. Even updating it involves recreating the container. The directories you map into it is what makes it "be the same". You should think of it more like you do about an .exe and less how you do about a VM in that sence. You also normally would not be updating the inside of your .exe with a package manager, you'd replace the entire .exe. Now substitute .exe with container and that's how for the most part you should think about containers.