More > JRiver Media Center 26 for Linux
Docker Container for JRiver Media Center 26
max096:
I made a bit of an organisational change to my docker containers git.
I've decided that moving forward it would be better to use gitlab.com instead of my privately hosted gitlab server!
The project has already been created here: https://gitlab.com/shiomax/jrivermc-docker
The main motivation to do this is to make it easier for people to create issues and possibly contribute to it in other ways if they want to. Before you would have required me to initiate account creation for you, to really do anything more than download the source.
I will also make a contribution guide when I get to it. But the gist of it is: If you want to do a merge request (gitlabs name for githubs pull requests). Don't work with the master branch, but with the dev branch and do merge requests into the dev branch. The master branch is actively being used to rebuild the current version with newer MC releases. So you should not try to merge (especially functional changes) into the master branch directly. You can try, but they will be rejected for that reason. That's basically all there is to it. :)
hells:
Hey Max, using your docker container. It's great but I've seen a couple issues, and for some reason GitLab is not cooperating and letting me log in.
Have you noticed that sometimes it just is a black screen? Requiring a container restart. Even with the maximize env var set. My other issue *might* be related to the container as I don't experience this on Windows/Mac clients, only on the container "server" itself: https://yabb.jriver.com/interact/index.php/topic,124616.msg862760.html
Any ideas?
max096:
--- Quote from: hells on March 25, 2020, 05:00:55 pm ---Hey Max, using your docker container. It's great but I've seen a couple issues, and for some reason GitLab is not cooperating and letting me log in.
Have you noticed that sometimes it just is a black screen? Requiring a container restart. Even with the maximize env var set. My other issue *might* be related to the container as I don't experience this on Windows/Mac clients, only on the container "server" itself: https://yabb.jriver.com/interact/index.php/topic,124616.msg862760.html
Any ideas?
--- End quote ---
It sometimes happens on amd64 and almost always happens on raspberry pies (witch is one of the reasons I really have no plans yet on when to put the arm images into the repository). Iīm working on gettting that to work on arm as the issue is very rarely happening for me on anything else. It also seems to me that itīs more likely to happen when the JRiver version updates. The maximize env does not have anything to do with it though. It only effects pop up windows.
JRiver is still running technically. You just canīt see it as it starts minimized for some odd reason.
The two ways to fix it for now is a container restart or you can also log into your container and switch to the jriver window.
--- Code: ---docker exec <container_name or id> /bin/bash
wmctrl -l # copy the hex id of JRiver Media Center window
wmctrl -i -a <hex_id>
--- End code ---
So the plan for version 8 so far would be that (mostly for arm sake, but it will absolutely effect am64 images) and also I want to start rebuilding all the images with new container versions down to I believe 26.0.22 was the one that forced pop pop-up / sub windows to stay on top of itself. That change made everything a lot easier.
hells:
--- Quote from: max096 on March 25, 2020, 07:59:24 pm ---It sometimes happens on x86 and almost always happens on raspberry pies (witch is one of the reasons I really no plans yet on when to put the arm images into the repository). Iīm working on gettting that to work on arm as the issue is very rarely happening for me on anything else. It also seems to me that itīs more likely to happen when the JRiver version updates. The maximize env does not have anything to do with it though. It only effects pop up windows.
JRiver is still running technically. You just canīt see it as it starts minimized for some odd reason.
The two ways to fix it for now is a container restart or you can also log into your container and switch to the jriver window.
--- Code: ---docker exec <id> /bin/bash
wmctrl -l # copy the hex id of JRiver Media Center
wmctrl -i -a <id>
--- End code ---
--- End quote ---
Great thanks! 1/2 way to this working how I wanted :D
Afrosheen:
Hi max096, thanks for updating the docker image of MC! I can finally feel comfortable moving away from my old setup where I was on MC22 via QNAP HybridDisk Station. It feels good seeing the new features that JRiver offers now.
I'm just having trouble with enabling Authentication in the media network. It seems that I cannot connect to a running instance of the media network when the authentication is enabled. But if disabled I can connect. It may be an issue with MC itself, but just wanted to know if you ran into the same issue?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version