More > JRiver Media Center 32 for Linux
Docker Images for MC32
Richard Martin:
--- Quote from: HaWi on January 29, 2024, 10:15:32 am ---I don't want to confuse things but I pulled
shiomax/jrivermc:latest
with docker-compose and a my yaml file and MC32.0.9 installed properly on my Synology NAS a few days ago.
--- End quote ---
I expect it's me...I pulled the latest image but was trying to use a container that was cloned from my MC31 container.
I'll get back to it in a few days and get it sorted
HaWi:
--- Quote from: Richard Martin on January 29, 2024, 12:27:55 pm ---I expect it's me...I pulled the latest image but was trying to use a container that was cloned from my MC31 container.
I'll get back to it in a few days and get it sorted
--- End quote ---
Ah, that explains it. I tried that, too at first and it also stayed with MC31.
I guess updating to a new major version requires "starting from scratch" so to speak.
Using docker-compose via CLI works pretty well for me. For updates within a major version I use Portainer and it takes only a minute to update.
Thanks to Max who has been very helpful to everyone.
Richard Martin:
I have now done a complete clean install to a new container and then restored a back up from 31.
This works fine and I can connect from my Windows client.
However, my NAS is set to shut down at night when no one is using it. The following day when the shiomax container restarts I am getting the following error in the log.
--- Code: ---useradd: user 'abc' already exists
--- End code ---
followed by
--- Code: ---s6-rc:warning: unable to start service setup-app: command exited 9
--- End code ---
The MC server doesn't start. I can connect to https:[server ip]/5800 but just get a black panel with "Not Connected" and a Reconnect button that does nothing.
Does anyone have any ideas what is going on here?
HaWi:
There also seems to be a lag between updates of different images. For example shiomax/latest-32.0.12-v0.4.2 (which is really the latest from JRiver) is available, whereas shiomax/latest is currently still pulling 32.0.9
HaWi:
--- Quote from: Richard Martin on February 02, 2024, 06:46:37 am ---I have now done a complete clean install to a new container and then restored a back up from 31.
This works fine and I can connect from my Windows client.
However, my NAS is set to shut down at night when no one is using it. The following day when the shiomax container restarts I am getting the following error in the log.
--- Code: ---useradd: user 'abc' already exists
--- End code ---
followed by
--- Code: ---s6-rc:warning: unable to start service setup-app: command exited 9
--- End code ---
The MC server doesn't start. I can connect to https:[server ip]/5800 but just get a black panel with "Not Connected" and a Reconnect button that does nothing.
Does anyone have any ideas what is going on here?
--- End quote ---
Have you tried to restart the Container from within the Docker Container Manager? That sometimes helps me when things go wrong.
Also, only somewhat related, a NAS is really supposed to run 24/7 and powering it down and up again every day puts unnecessary stress on the hardware, especially the drives. My personal recommendation would be to keep the NAS running at all times.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version