More > JRiver Media Center 25 for Linux

QNAP Hybrid disk station licence

<< < (2/4) > >>

max096:

--- Quote from: brains4eva on July 15, 2019, 11:46:40 am ---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...

--- End quote ---

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:

--- Quote ---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...
--- End quote ---

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:

--- Quote from: Scobie on July 15, 2019, 06:24:13 pm ---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.

--- End quote ---

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...

Navigation

[0] Message Index

[#] Next page

[*] Previous page