More > JRiver Media Center 25 for Linux
JRiver MC25 Docker Image with WebUI as VNC
balky:
--- Quote from: max096 on August 02, 2019, 05:38:54 pm ---A bit drastic actions..., but great that it works now! :)
--- End quote ---
Yes, quite drastic, and I fully agree... I'm at the point where after 10+ years constantly installing / uninstalling / reinstalling, it has become kind of effortless to throw anything that doesn't work as expected out the window... :)
In the 10+ years, only JRiver (for audio only) survived the constant cleanup / replace process...
The only thing left (for me) now is to have a docker image that will allow JRiver to be set as a DLNA renderer only.
The docker image only needs to be able to use the audio card. I will be all set with JRiver forever if this would be possible.
shortie:
--- Quote from: max096 on July 30, 2019, 05:03:36 pm ---Do you still have that directory that bailed? If so Im curious if the current container would fix that. Any of them. I think with the current container even if a window where to pop up behind something it should be pulled in front right after the window changed.
Otherwise, could you send me said directory confidentially? Just send me a private message then, not a good idea to post folders that potentially contain license information on a public forum.
--- End quote ---
Well, I was just gonna try with your newest image and find that the trial expired on that directory. I guess I could license it. Thoughts?
max096:
--- Quote from: shortie on August 04, 2019, 12:19:21 pm ---Well, I was just gonna try with your newest image and find that the trial expired on that directory. I guess I could license it. Thoughts?
--- End quote ---
Have you maybe put the directory on another PC? I'm not sure if the license does stay active then. Never tried that. But otherwise it should stay active when up or downgrading the container. I've done that multiple times on the two installs of that container I have now (that are activated).
Just tried that. The license expires when you put the folder on another PC you'll have to re-enter your license.
Now it does not stay activated on that install where I got the folder from anymore either. I'm not sure yet. Maybe it solves itself. It does not even work on the older container versions where it most definitely worked before. Maybe it solves itself. Otherwise I'll have to look into it.
I also did just rebuild a new container witch would contain all the newest debian updates and all the packages (besides jriver) that's not it either.
And it does not seem to work on jatzoo's image either.
Both (seem) to activate until you shut down the container, then you are back to the trial license.
This is new, I'm not sure what's going on quite yet.
But more importantly. Did it updating that fix the gui? xD
shortie:
--- Quote from: max096 on August 04, 2019, 05:03:52 pm ---Did it updating that fix the gui? xD
--- End quote ---
i haven’t been able to check that yet. Guess I’ll have to install a license but may not be able to get to it until the weekend. I’ll report back when I have a chance to try it.
max096:
I found out why the activation is not persisting. This isn't because the container is recreated, but because when you have a container with the default bridge networking and you recreate the container it will also create a new network. When you create a new network your license will be gone.
Since on my main install I'm using host networking the license persisted when upgrading. (With host networking you use.. well your hosts network, so you never end up creating and removing virtual docker networks).
I'll be updating the readme with those new findings. On my main install I actually use host networking. Hence it always worked. And I didn't feel like messing with it, I usually mess with other installs that are usually not around for long enough to bother activating them.
The only downside of host networking is that you cannot remap ports. And it also is not automatically accessible from the outside (as it is usually the case with bridge networking). You will end up having to configure either firewalld, ufw or just straight iptables. Depending on your distro or preference.
There should be workarounds for this with bridge networking too. At this current time I don't know of any (gotta try that too). R.I.P. my restore keys (not yet, but I've already gone threw 10 or so). But I'm sure there are ways to re-use a network (but not sure how convenient that is to administer without extra tooling). And there may be ways to specify the network in the command and in the compose file in a way that it will recreate a similar enough network for jriver to not throw away your license on re-creation (witch would include every single up and downgrade).
---
I also added a little bit of a firewall configuration section into the readme for ufw and firewalld. Depending on what you are using. Since that would be needed when using host networking. Unless you just don't run any firewall at all.
Funny how <?xml version="1.0" encoding="utf-8"?> breaks markdown on dockerhub, without escaping it and all the rest that looks like html. -.-
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version