More > JRiver Media Center 26 for Linux
Docker Container for JRiver Media Center 26
BryanC:
--- Quote from: Dantesjoe on May 31, 2020, 04:10:10 pm ---My actual folders of music are contained at "/volume2/oldmusic/"
--- End quote ---
There's the issue. You need to set the "file/folder" to that directory and the "mount point" to the internal mount location of the container. I don't know if your container defaults to particular directories but it may be easiest for you to just mount your directories to the same location within the container. This would also make it easier to share libraries between the containers or use neat tricks like playing local files while using a remote library.
merman-corrode-portage:
Hey Max, thanks for your container, I've been using it since you posted here back in January. However since installing I've had a nagging warning I though I might bring up:
--- Code: ---[0606/050306.068755:WARNING:discardable_shared_memory_manager.cc(194)] Less than 64MB of free space in temporary directory for shared memory files: 63
--- End code ---
max096:
--- Quote from: merman-corrode-portage on June 05, 2020, 09:57:59 pm ---Hey Max, thanks for your container, I've been using it since you posted here back in January. However since installing I've had a nagging warning I though I might bring up:
--- Code: ---[0606/050306.068755:WARNING:discardable_shared_memory_manager.cc(194)] Less than 64MB of free space in temporary directory for shared memory files: 63
--- End code ---
--- End quote ---
As long as you never got a follow up error such as "'No space left on device'" in all this time it should be totally save to ignore.
There is this discussion on github https://github.com/moby/moby/issues/12940 seems to suggest that this was fixed quite a while ago in a docker update.
What OS and what docker version are you using?
vickozagi:
Hi,
I am using openmediavault and only Compose file format version 2 is supported. So with my limited knowledge I rewrote the compose file. Everything works except access to the music folder. If I drop the music in config folder I can play music on all endpoints. Does anybody know what I did wrong?
---
version: "2"
services:
jrivermc26:
image: shiomax/jrivermc26
container_name: jrivermc26
restart: always
environment:
- TZ=America/Los_Angeles
- VNC_PASSWORD=12345
volumes:
- /srv/dev-disk-by-id-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5XU8213-part1/config/jrivermc26:/config:rw
- /srv/dev-disk-by-id-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4NKPA1P91-part1/Muzika/SQB:/data/music:rw
network_mode: host
max096:
--- Quote from: vickozagi on June 17, 2020, 01:24:34 pm ---Hi,
I am using openmediavault and only Compose file format version 2 is supported. So with my limited knowledge I rewrote the compose file. Everything works except access to the music folder. If I drop the music in config folder I can play music on all endpoints. Does anybody know what I did wrong?
---
version: "2"
services:
jrivermc26:
image: shiomax/jrivermc26
container_name: jrivermc26
restart: always
environment:
- TZ=America/Los_Angeles
- VNC_PASSWORD=12345
volumes:
- /srv/dev-disk-by-id-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N5XU8213-part1/config/jrivermc26:/config:rw
- /srv/dev-disk-by-id-ata-WDC_WD30EFRX-68EUZN0_WD-WCC4NKPA1P91-part1/Muzika/SQB:/data/music:rw
network_mode: host
--- End quote ---
The config looks right. Are you sure the second path to your music folder is right? The path to the music folder is a bit different.
What version of compose you use really does not matter at all as long as it supports the configuration you want to do. Its just a convenience tool for creating containers. Im just using it because it gives you a config file so when you wanna upgrade your container its easy to do with the same configuration. Otherwise, you'd have to keep track of your entier docker run command. Solutions like openmediavault may have tools in place that make this advantage irrelevant.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version