Hi Paul,
I started using the Synology version of Songkong Pro.
Now you announced a new release.
How do I update the docker container???
Thanks
Claas
Update Synology version
Hi just stop your container and delete image. Then redownload image and reconfigure, the latest image has been updated to the new version.
Thanks.
Is there a plan/possibility to change that?
Because this means that I need to reenter my license every time I update.
A bit annoying, not?
In general I must admit that the NAS version is just great.
Much faster though I do only have a 1511+.
Cheers
Claas
That isn’t the case, at least if you configure a config folder as described in the notes because the license is stored there, as license.properties. So when you install a new image and run as a container it shoud pick up the existing license.
Ok. That wasn’t clear to me. Thanks.
Hi Paul
I installed songkong and got it working with a little bit of wrestling with my brain…
You have updated it, and I see that I need to stop the container and delete the image, then install the new image…
I am unable to stop the container, it restarts itself…“delete” is greyed out…
What should I do…
dave
Are you getting Container and Image confused you should be able to stop the container and then delete the image.
Hi Paul
thanks for the response…
No, I’m not confusing the container with the image…not obviously at least.
when i stop the container…it restarts itself…instantly…!
dave
What are you running SongKong on ?
Its a Synology twin bay 716 nas…also running Minim…
dave
So you click on the switch to stop it and it just restarts immediately ?
Do you have Enable auto-restart" setting enabled under Docker > Container > Edit > General Setttings, if so uncheck it.
Hi Paul
I thought you had it there…however, I am unable to find an auto- start function anywhere, even though I followed your instruction to the tee.
the “edit” button is greyed out…there is no auto start under the settings tab…
stumped…!
dave
Hi Paul,
I solved it by removing / uninstalling docker and all images…
Then re-installed docker, and then songkong…
Seems to be all A-OK…
Cheers
dave