Print

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

[Scobie]

Same, I do an apt-get and it doesn't find any MC updates since MC29.64

[cassfras21]

Great job max!

I tried your Docker image and adopted it.
The web UI is fantastic. Even with vnc, the GUI is much smoother and more responsive than in my own docker image built for mc21 and mc22.

I had to renew my mc23 license but it's worth it

Besides that, I figured out how to mount my DAC plugged into my Synology in the container. Now my Syno acts as an audio player with mc29!

If it helps other syno owners, to mount your DAC in a docker container you need to:
-install the same modules as the audio station is requiring for playback. By installing Audio Station or a custom script.
-fix permissions for audio device. By default, the audio device is initialized to be accessible only by the root user.

Code: [Select]

chmod a+rw /dev/dsp*
chmod -R a+rw /dev/snd/


[max096]

Great job max!

I tried your Docker image and adopted it.
The web UI is fantastic. Even with vnc, the GUI is much smoother and more responsive than in my own docker image built for mc21 and mc22.

I had to renew my mc23 license but it's worth it

Besides that, I figured out how to mount my DAC plugged into my Synology in the container. Now my Syno acts as an audio player with mc29!

If it helps other syno owners, to mount your DAC in a docker container you need to:
-install the same modules as the audio station is requiring for playback. By installing Audio Station or a custom script.
-fix permissions for audio device. By default, the audio device is initialized to be accessible only by the root user.

Code: [Select]

chmod a+rw /dev/dsp*
chmod -R a+rw /dev/snd/


Ähm I'm not quite sure which one did you try? The shiomax/jrivermc-dockerxx or  shiomax/jrivermc-docker-next?

The "next" is not completely done yet. Might be a bit misleading because "v0.0.1" is on dockerhub. There have been actually many "v0.0.1". Kinda in the process of finishing up the build / publish pipeline. Then Ill remove that (currently) sad and empty general menu. And then do some testing and leave that be actual  v0.0.1. Gonna tell you when thats there.

Screen resizing is still not going to be done for (actual) v0.0.1. Not sure how I wanna do that yet, but Ill figure something out eventually. It's only going to be built for arm64 and amd64 for now (so no 32 bit arm). Technically, it works just fine on 32bit arm but as i build those on an actual physical raspi and only have one of those to dedicate to this I have to pick one.

[cassfras21]

Ähm I'm not quite sure which one did you try? The shiomax/jrivermc-dockerxx or  shiomax/jrivermc-docker-next?

I tried shiomax/jrivermc-dockerxx which I compared to cassfras21/jrivermc.

[max096]

I tried shiomax/jrivermc-dockerxx which I compared to cassfras21/jrivermc.

Yeah figured that much. The new one is not really quite done yet as I said if you wanna see what's up with that you can try the shiomax/jrivermc-docker-next:latest-amd64 or latest-arm64 tags. Don't try latest (or any of the "multiarch tags"). Turns out dockerhub was not 'not updating my image' but docker appearenly caches the manifest and will not make a new one if one was already created locally (gotta cache those kilobytes..). So the multiarch tags are currently outdated broken versions that don't work at all.

The main reasons for creating a new image was that the old one didn't work well on arm and I wanted more control in terms of functionality looks/feel of the webgui. I wrote a bit of a longer post about that earlier. The current image uses a base image that comes with a webgui. It's more for general use for any application. If you want to do something specific for one specific application there was no clean way to do that without making my own from scratch.

[bob]

Looks like I forgot to update the repo.
Sorry.
It's updated now.

[HaWi]

apt-get now downloads .66 on my rPi but in Docker (using Portainer to recreate the container) I still get .64
EDIT: Pulling shiomax/jrivermc29:29.0.66-latest-17 with docker-compose works fine. I have 29.0.66 running on my Synology now.

[Scobie]

Using apt-get from Container Station Terminal on the QNAP now pulls down .66 using shiomax/jrivermc29:latest.

Thanks Bob.

[cncb]

Looks like 86 was pushed several days ago but latest still downloads 66?

[HaWi]

Looks like 86 was pushed several days ago but latest still downloads 66?

Yes, it's been like this since the version before. With docker-compose I get the correct version.

[max096]

The release notes state that it's not in the apt repo yet because of technical reasons. :latest gets you what was in the repo at the time of building it.

[HaWi]

The release notes state that it's not in the apt repo yet because of technical reasons. :latest gets you what was in the repo at the time of building it.

Thanks Max
I don't know how these things work but the :latest in Docker Hub seems to be .66 as well even though .86 has been uploaded before that. So when I use Portainer to re-create the MC container it pulls .66. The first time this happened was with the update to .66, when it would consistently install the previous version.

[max096]

Thanks Max
I don't know how these things work but the :latest in Docker Hub seems to be .66 as well even though .86 has been uploaded before that. So when I use Portainer to re-create the MC container it pulls .66. The first time this happened was with the update to .66, when it would consistently install the previous version.

Yes, because :latest uses the apt repository and it´s not on the apt repository .86 is from a .deb file. It´s currently a bit inconsistent because for the current images some of the 29.x.xx are also using the repository. That will be different for the new images every single one of the tags where you specify the full mc version number will be built with a .deb file and not only some of them. I think if you specify a mc version in the tag you actually really do want exactly that version and therefore apt update should not update it either. And it´s just a bit more consistent that way.

Still got some things to sort out. But it´s getting along. Resolution resizing is also working (thought that would be hard but it actually really wasn´t). You can specify the initial resolution as environment variables and you can change it on a per client basis in the web GUI also.

[chrisG81]

Hello,
I installed it on my Synology and it works great. Thank you for the effort.
Now I have a problem to activate the license. I tried it via the menu. I tells me I have the wrong version. I use the key which I received after purchasing the MasterLicense for MC30.
I also tried to do it with the .mjr file. I logged in via SSH with my admin account. If I want to execute the first command you have described "docker exec -it jrivermc /bin/bash" I receive a permission denied. Maybe this could be a problem with synology.

Installing the Lincense on my MAC worked.

Thank you for your help!

Update:
I was now able to ssh in the docker container. Same reply: Please download and install the version that matches your license...

Update 2:
Now it works, after updating the container -- Thank you

[max096]

Hello,
I installed it on my Synology and it works great. Thank you for the effort.
Now I have a problem to activate the license. I tried it via the menu. I tells me I have the wrong version. I use the key which I received after purchasing the MasterLicense for MC30.
I also tried to do it with the .mjr file. I logged in via SSH with my admin account. If I want to execute the first command you have described "docker exec -it jrivermc /bin/bash" I receive a permission denied. Maybe this could be a problem with synology.

Installing the Lincense on my MAC worked.

Thank you for your help!

Update:
I was now able to ssh in the docker container. Same reply: Please download and install the version that matches your license...

Update 2:
Now it works, after updating the container -- Thank you

For the permission thing you have to add yourself to the docker group to be allowed to run docker commands without being root.

I think you still need to use :29.0.86-latest-17 instead of :latest with mc30 licenses.

[xdeyzaguirre]

Thanks,
With QNAP, Docker amd JRMC29 I have my Music in any place.

[yukibarr]

First docker images for MC29. 

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

Make sure to backup your library first, as usual, major version changes will not bring your stuff over automatically.

max096, any chance you could post a step-by-step installation guide? I would like to rum JRiver 29 on my Synology NAS.  Many thanks in advance

[yukibarr]

First docker images for MC29. 

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

Make sure to backup your library first, as usual, major version changes will not bring your stuff over automatically.

max096, any chance you could point me to or post a step-by-step installation guide? I would like to rum JRiver 29 on my Synology NAS.  Many thanks in advance