More > JRiver Media Center 26 for Linux
Docker Container for JRiver Media Center 26
Afrosheen:
--- Quote from: max096 on January 10, 2020, 10:05:27 am ---I figured out what was wrong. In the start command of MC I set the home directory to /config and in the command I now entered I did not do that.
So this is how you can activate the container with the mjr file. First get the mjr file and place it into the config folder. I just named it key.mjr, because I copied it with scp and it was less to type. Also my container is named jrivermc26, yours might have a different name.
--- Code: ---docker exec -it jrivermc26 /bin/bash
exec env HOME=/config mediacenter26 /RestoreFromFile /config/key.mjr
--- End code ---
As I said I'm probably gonna just make this happen on startup when the config directory contains any file with the .mjr extension. But for now this works.
I have just pushed a new version of it. It looks for .mjr files within the config directory every 30 seconds. When it finds one it tries to activate jriver with it. If it's successful it get's rid of the .mjr file.
--- End quote ---
Hi, I hope this message receives you all well. I'm having trouble with keeping the app licensed upon restarting my NAS. Each time I restart I have to retype the license key before being able to use the app. Instead of doing that, I'm trying to follow your method of just having the license key file stored in the "config" folder, but one wasn't created when I installed it via QNAP's Container Station app. I've created a screenshot of the folder structure and have placed the file in every folder that seems reasonable, but no avail. I'm not familiar with using the command line with QNAP's Container Station. I appreciate the consideration.
Scobie:
You can get around this issue by assigning a Mac address to the container. The license blows up because it is looking for the same Mac address it used before and when it doesnt find it it assumes it is running on a different host.
Doesn't have to be a accurate, just valid, and there are places online to generate one.
max096:
--- Quote from: Afrosheen on August 10, 2020, 06:06:55 pm ---Hi, I hope this message receives you all well. I'm having trouble with keeping the app licensed upon restarting my NAS. Each time I restart I have to retype the license key before being able to use the app. Instead of doing that, I'm trying to follow your method of just having the license key file stored in the "config" folder, but one wasn't created when I installed it via QNAP's Container Station app. I've created a screenshot of the folder structure and have placed the file in every folder that seems reasonable, but no avail. I'm not familiar with using the command line with QNAP's Container Station. I appreciate the consideration.
--- End quote ---
Was this resolved now? By the looks of it your _data folder is mounted to /config. Since the user chooses the path to mount it to the only way I can refer to it is "the config directory", in your case it means _data then.
The MJR file won´t help you if your license key gets accepted. It´s only a fallback way to activate if the license key does not work at all.
As @Scobie said you might have to specify a mac address for the license to stay activated (this is only neccessary when using bridge networking). If you do not need the ablity to remap ports I would recomend you use host networking, then you also do not need to specify a mac address as it uses your hosts network interface instead of generating a virtual one.
Afrosheen:
Yes it’s resolved! Thank you!! I just rebuilt the container with a specified MAC address last night and then restarted and it opens without the splash screen!
I’ve had to build it with bridge networking because using the same LAN IP as the NAS itself makes things go haywire. Maybe I’m missing something but I just wanted to get a stable MC server running again.
Thanks again for the help @Scobie & @max096
HaWi:
--- Quote from: Afrosheen on August 12, 2020, 01:35:54 pm ---
I’ve had to build it with bridge networking because using the same LAN IP as the NAS itself makes things go haywire. Maybe I’m missing something but I just wanted to get a stable MC server running again.
--- End quote ---
Strange, I am running MC in host mode on my Synology DS1891+ and, apart from all the rookie mistakes I made, I haven't had a problem. I activated MC in docker by using the MC27 master license .mjr key file through the WebUI. I do have to put in the Access Key every time I reload the UI on my browser, though.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version