More > JRiver Media Center 25 for Linux

JRiver MC25 Docker Image with WebUI as VNC

<< < (14/14)

shortie:
Hmmm...i already have a service running on port 5900 and can’t change it easily so i guess, given everything, MC won’t be in production for me for a while. Wait, what about changing the container’s VNC port or making it a parameter? The other ports are peculiar to MC so they shouldn’t collide with anything else, right?

I still think, though, that JRiver should distribute an official container...but not at the expense of continued Linux development :)

max096:

--- Quote from: shortie on August 05, 2019, 10:49:58 pm ---Hmmm...i already have a service running on port 5900 and can’t change it easily so i guess, given everything, MC won’t be in production for me for a while. Wait, what about changing the container’s VNC port or making it a parameter? The other ports are peculiar to MC so they shouldn’t collide with anything else, right?

I still think, though, that JRiver should distribute an official container...but not at the expense of continued Linux development :)

--- End quote ---

Turns out all that needs to be changed for bridge networking is specify a mac-address in the compose file or docker run command.


--- Code: ---version: '3'
services:
  jrivermc25:
    image: shiomax/jrivermc25
    restart: always
    container_name: jrivermc25
    mac_address: ed:e8:60:2d:65:c1
    ports:
      - "5800:5800"
      - "5900:5900"
      - "52100:52100"
      - "52101:52101"
      - "52199:52199"
      - "1900:1900/udp"
    environment:
      - VNC_PASSWORD=12345
    volumes:
        - /path/to/config:/config:rw
        - /path/to/music:/data/music:rw

--- End code ---


--- Code: ---docker run -d \
    --name=jrivermc25 \
    --net=bridge \
    --restart=always \
    --mac-address=ed:e8:60:2d:65:c1 \
    -p 5800:5800 \
    -p 5900:5900 \
    -p 52199:52199 \
    -p 52101:52101 \
    -p 52100:52100 \
    -p 1900:1900/udp \
    -v config:/config:rw \
    -v /path/to/music:/data/music:rw \
    -e VNC_PASSWORD=12345 \
    shiomax/jrivermc25

--- End code ---

As long as your mac address does not change your license does not expire and require re-activation. But keep in mind bad things might happen if you have two machines on the same network with the same mac addresses. So if you are having more than one container. Use different mac addresses. You can find plenty of mac address generators online.

Thanks for the help @bob! ;D I would have tried to keep the entire virtual network alive. This makes it much easier.

max096:
Updated the image a bit

Version 2 Changelog

* xpropspy now uses sh instead of bash (microoptimization sh is faster, but can do less)
* ascii art on startup and environment variable ENABLE_SIGNATURE (1 by default)
* specifying debian-9-v3.5.2 instead of latest, witch is currently equivalent (to avoid breaking the image on automated builds)
* removed layer below for main jriver window from rc.xml as no longer needed (also seems to have fixed some ui gliches in the integrated webgui. The one inside jriver, for cloudplay and so forth.)
* added option MAXIMIZE_POPUPS to maximize every window that has the name "JRiver Popup Class" (0 by default)

Navigation

[0] Message Index

[*] Previous page