More > JRiver Media Center 24 for Linux

JRiver Media Center - Docker image

<< < (4/9) > >>

cassfras21:
I guess you are trying to achieve this with a LUN volume but you're wrong
<local_media_volume> is the directory path to your local media folder on your nas.

For example if have your music is in the directory /home/user/music


--- Code: ---docker run -d \
--name=jrivermc22 \
-e ENV_UPDATE=no \
-e ENV_VNCPASS=jriver \
-h 192.168.0.100 \
-p 5905:5900 \
-p 52195:52199 \
--volumes-from jrivermc22--data-container \
-v /home/user/music:/mnt/media/music \
cassfras21/jrivermc
--- End code ---

NoFace:

--- Quote from: cassfras21 on January 13, 2017, 10:55:33 am ---I guess you are trying to achieve this with a LUN volume but you're wrong
<local_media_volume> is the directory path to your local media folder on your nas.

For example if have your music is in the directory /home/user/music


--- Code: ---docker run -d \
--name=jrivermc22 \
-e ENV_UPDATE=no \
-e ENV_VNCPASS=jriver \
-h 192.168.0.100 \
-p 5905:5900 \
-p 52195:52199 \
--volumes-from jrivermc22--data-container \
-v /home/user/music:/mnt/media/music \
cassfras21/jrivermc
--- End code ---

--- End quote ---

That seems to have done the trick. Thank you

I can now see all my files and ive imported my library from previous library and everything is valid and present and working  :).

Just a little stuck on the networking. Its showing as 10.0.3.2 but my network is the regular 192.168.0... etc. How do i get the contain to work with my network so i can access jriver remotely.

Sorry for my noob-ism, still new to linux.

cassfras21:
This is the default way docker works with networks. If you don't use DLNA/uPnp with JRiver you have nothing to change.
Based on your settings, if your nas IP is 192.168.0.10, JRiver should be accessible at 192.168.0.10:52195

Now if DLNA matters for you, you should consider to run the other app container starting with


--- Code: ---docker run -d \
--name=jrivermc22 \
--net=host \
--pid=host \
--- End code ---

With this settings, your container will be on the same subnet and have the exact same IP than your Nas. It is necessary to allow SSDP broadcasting and so DLNA devices discovering.

JimH:

--- Quote from: cassfras21 on January 14, 2017, 03:13:19 am ---... JRiver should be accessible at 192.168.0.10:52195

--- End quote ---
If that doesn't work, try 192.168.0.10:52199

NoFace:

--- Quote from: cassfras21 on January 14, 2017, 03:13:19 am ---This is the default way docker works with networks. If you don't use DLNA/uPnp with JRiver you have nothing to change.
Based on your settings, if your nas IP is 192.168.0.10, JRiver should be accessible at 192.168.0.10:52195

Now if DLNA matters for you, you should consider to run the other app container starting with


--- Code: ---docker run -d \
--name=jrivermc22 \
--net=host \
--pid=host \
--- End code ---

With this settings, your container will be on the same subnet and have the exact same IP than your Nas. It is necessary to allow SSDP broadcasting and so DLNA devices discovering.

--- End quote ---

I was connecting to the default port which is why it wasn't connecting  :-[. now running on 52195 and all is well  :)
Just about to hit the delete key on my window vm now  ;D

Thanks again for all your help


--- Quote from: JimH on January 14, 2017, 05:45:56 am ---If that doesn't work, try 192.168.0.10:52199

--- End quote ---

Yeah that was the issue i was trying to connect to 52199 instead of 52195. Now everythings working flawlessly  :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page