More > JRiver Media Center 25 for Linux
JRiver MC25 Docker Image with WebUI as VNC
bob:
I'm not sure I'm totally following this but in general you don't want to alter anything in the home directory at all between container runs.
Also, if there are window size/position issues, we just added an option to the Tree and View settings to reset all of window size/position settings to default upon the next run.
max096:
--- Quote from: bob on August 01, 2019, 10:08:49 am ---I'm not sure I'm totally following this but in general you don't want to alter anything in the home directory at all between container runs.
Also, if there are window size/position issues, we just added an option to the Tree and View settings to reset all of window size/position settings to default upon the next run.
--- End quote ---
Yes, but shortie had a home directory that somehow made problems and I wanted to know if this is still the case (appearently he fixed it by making a new one). If thats still the case having the folder would make potential fixes testable. Although, seems like no one else really had that problem yet. Its quite possible its already not a problem (since 15th last months more precisely), But since I never figured out how to reproduce it, I dont know.
Thanks for the extra setting, could be useful.
However, since shortie had a problem of the about window popping up behind jriver. Depending on how it where to break you may not be able to get to the settings.
Can you add that option as a startup option "mediacenter25 /resetgui" or something like that? Then I could be adding an environment variable (or similarly) for that to start it with that option, that you can enable to recover from broken ui states.
balky:
No matter what I do, I can't seem to fix network problems when trying to run this docker image on OpenMediaVault 4.
I need to set the version to 2 in the .yml file, otherwise docker compose won't work, and when it does works, all ports are listening on 0.0.0.0
Has anyone been able to get this to run on any version of OpenMediaVault?
Thanks
max096:
--- Quote from: balky on August 02, 2019, 07:22:39 am ---No matter what I do, I can't seem to fix network problems when trying to run this docker image on OpenMediaVault 4.
I need to set the version to 2 in the .yml file, otherwise docker compose won't work, and when it does works, all ports are listening on 0.0.0.0
Has anyone been able to get this to run on any version of OpenMediaVault?
Thanks
--- End quote ---
What does docker inspect have to say about the network configuration of the container you made with v2 and v3?
Either way if v2 works fine. It is perfectly fine to run that since the version in the compose file refers to the version of the configuration file standard. It has no affect on what docker, or docker-compose version you are using. There are newer docker-compose.yml versions, but those are more targeted towards docker-swarm.
Have you tried host networking? That does work? Bridge networking is not really working on my centos ovirt NAS either, because of the firewall rules and networks ovirt setup. But host networking works and bridge networking works in VMs ovirt can host. So it may be the same thing for your openmediavault.
(EDIT: Got this part wrong at first. Now its right. The part where it sais "HostIp" made me check that again. Since that would not really make much sence otherwise, for what I initially believed it to be. Either way, I never needed to specify an IP there.)
When you run docker inspect this is kinda whatīs expected when using bridge networking. I mapped the two VNC port(s) to different ports on the host. The 0.0.0.0 part is the host. You (or I) didnīt specify any IP, the 0.0.0.0 means as far as docker is concerned any host IP is valid.
You can specify an IP if you need one. Such as 192.168.1.2:5800:5800 witch would mean itīs only reachable at 192.168.1.2. Meaning if you put an IP there and run a container locally 127.0.0.1:5800 will not work. Accessing 192.168.1.2:5800 would work. With 0.0.0.0 both work. If you have multiple networks, you can restrict what networks have access to it in that way.
--- Code: --- "NetworkSettings": {
"Bridge": "",
"SandboxID": "b9018903c4afaf3f46ce32a6881a321a4789b51620074cbb5627a1c142612c7b",
"HairpinMode": false,
"LinkLocalIPv6Address": "",
"LinkLocalIPv6PrefixLen": 0,
"Ports": {
"1900/udp": [
{
"HostIp": "0.0.0.0",
"HostPort": "1900"
}
],
"52100/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "52100"
}
],
"52101/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "52101"
}
],
"52199/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "52199"
}
],
"5800/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "5810"
}
],
"5900/tcp": [
{
"HostIp": "0.0.0.0",
"HostPort": "5911"
}
]
}
--- End code ---
bob:
--- Quote from: max096 on August 02, 2019, 03:24:05 am ---Yes, but shortie had a home directory that somehow made problems and I wanted to know if this is still the case (appearently he fixed it by making a new one). If thats still the case having the folder would make potential fixes testable. Although, seems like no one else really had that problem yet. Its quite possible its already not a problem (since 15th last months more precisely), But since I never figured out how to reproduce it, I dont know.
Thanks for the extra setting, could be useful.
However, since shortie had a problem of the about window popping up behind jriver. Depending on how it where to break you may not be able to get to the settings.
Can you add that option as a startup option "mediacenter25 /resetgui" or something like that? Then I could be adding an environment variable (or similarly) for that to start it with that option, that you can enable to recover from broken ui states.
--- End quote ---
MC child windows shouldn't popup behind the main MC window. We never specify underneath stacking and we don't alter the stacking order. You can get a window to go behind by clicking on the main window while the popup is showing IF there is a window manager since that's out of the control of MC. We've done some preliminary work to restack in that case but it's not as simple as it seems since many windows in MC are a collection of windows.
When there is a window manager ALT-Tab generally cycles through the windows. When we had a QNAP version, their window manager forced every open window to fullscreen so that it was impossible to restack the windows by accident.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version