More > JRiver Media Center 25 for Linux

JRiver MC25 Docker Image with WebUI as VNC

(1/14) > >>

max096:
I just wanted to share this with you guys. i made my own docker image now that I wanted to do for quite a while, but had a few problems along the way.
However, now it's fully working (I think).

You can find the source here (and description on how to use it and so forth): https://gitlab.shio.at/max/jrivermc25-docker
And the dockerhub: https://hub.docker.com/r/shiomax/jrivermc25

It's based on https://github.com/jlesage/docker-baseimage-gui and as such comes with the same webgui all his docker images use to use as an alternative to a VNC client. You can still use a VNC client with it. But I mostly won't anymore.

The only other public image for jrivermc25 currently seems to be one built by jatzoo (been using his 24 image before). I first thought this one would come out to be a lot bigger, but it actually isn't. It's around 100mb smaller to my own surprise. Not sure how much that means about being the most lightweight it can be. Either way I'm not very concerned with that. I want it to work and be convenient.

If you are trying to use it and have any problems with it. You can report them here.

JimH:
Thanks!

Scobie:
Nice one thanks Max. Is the WebUI the key difference between this and the existing docker image?

Cheers

max096:
From a user perspective probably. More or less. Technically its very different, it was built from scratch, because the base image ive used installs some software that's different. Like s6-overlay instead of supervisord. It uses volume mounts instead of a data container. And it does use openbox instead of nothing. Most of those choices were made by the creator of the base image, not really by me. I wasnt familiar with most of it, but rolled with it anyway. It wasnt really that hard, other than I had to write some service script to prevent jriver from being minimizeable. Not sure if what I did is the best way to do it, but I didnt have to turn the base image upside down to achieve it.

The other docker images for jriver all seem to be essentially this one https://github.com/cassfras21/docker-jrivermc with a different jriver version installed.

max096:
Whats also cool that I used the gilab ci pipeline for building the containers. So automated scheduled builds can be enabled with like a click of a button. I dont do that (yet) for stable and latest. But I probably will at some point and fork off working tags like 25.0.50. Its not really that likely that a rebuild would break latest and stable, I dont think, but its definitely possible. But that would keep the image from being outdated, really ever. If you wanna keep using to the same image you'd just use the version tags instead.

But if you want the latest stable or latest latest version, you won't have to build it from source that way.

Navigation

[0] Message Index

[#] Next page