Synology Docker MS2.1 update

[jamief]

Hi

I'm struggling to successfully update to MS2.1 on DSM7 where I use MS in a Docker container. I've deactivated the full licence (which has 6 months to run) in the WebUI. I've stopped MS (Docker) in MW, though container is still active. Old MS package is stopped in DSM.

When I try to update, I get the message in Package Manager "Failed to Update... Your updates entitlement expired (around my last renewal date in November)... ".

Have I misunderstood the licencing or am I doing something wrong? Sorry if this is answered elsewhere... I looked but couldn't find it.

Thanks

[simoncn]

Did you renew your updates license when it expired last November? If not, you will not be able to install any new versions or updates released since that date.

Edit: I checked the license database and I have confirmed that you have an active subscription, so you should be able to install MinimServer 2.1.2 from DSM Package Center.

Edit 2: It looks like your license for MinimServer 2.0.18 is still active on DSM and in your Docker container. I suggest you do the following:

1) Start MinimServer 2.0.18 in DSM. This ensures the updates expiry date is correct on your Synology as well as in the license database.
2) Install MinimServer 2.1.2 in DSM. This should now work because you have previously done step 1.
3) Start MinimServer 2.0.18 in your Docker container and use the web UI to export your profile.
4) Stop MinimServer 2.0.18 in your Docker container.
5) Create a new Docker container for DSM 2.1 and use the web UI to import the profile that you exported in step 3.
6) When you are sure the new Docker container is working correctly, delete the old Docker container.

It is not essential to do step 2 but this is a good idea because it keeps your MinimServer version consistent everywhere on your machine. It is essential to do step 1. If you have not done step 1 since last November, I think this is why you have had this problem. I will change the wording of the renewal email to clarify this for other users in your situation.

[jamief]

Hi Simon

Thanks for the rapid reply.

(18-05-2022 08:58)simoncn Wrote:  Edit: I checked the license database and I have confirmed that you have an active subscription, so you should be able to install MinimServer 2.1.2 from DSM Package Center.

Any clues on why it doesn't work? Do I need to stop the Docker container? I do use a macvlan network configuration for Docker to help manage port conflicts / complexity, but this has never presented a problem before for installing and using MS. There is a bridge to the host.

Thanks

[simoncn]

Please see Edit 2 in my reply above.

[jamief]

Hi Simon

Thanks for the suggested steps. While I got there in the end, it wasn't so easy. I'll include my experience in case it helps anyone else who runs into difficult with Docker updates.

- Steps 1 & 2 fixed the fundamental problem of the error during DSM package installation
- I use Portainer to manage Docker containers, and not for example Docker compose, so it is easier for me to migrate an existing container definition to keep all the network, volume & port mappings. This meant that I couldn't strictly follow your steps 5 & 6. Also for Docker use without compose, if you use MinimStreamer, you need to remember to copy ffmpeg to somewhere in the path like /usr/bin in the container (I keep a copy in the mapped MinimServer volume, then go to the container's console in Portainer and enter "cp MinimServer/ffmpeg /usr/bin").
- I'm completely confused about profiles. It looks to me like they aren't working. I clicked to export my default (active) profile, but I subsequently couldn't find anything saved with current date in the MinimServer folder or subfolders (maybe not saved because it hadn't changed). I had an old one on my PC that I imported, however, I've not be able to "activate" it. Similarly, I can't "view" any profiles: they are listed, but View window shows nothing. As my config did restore, I guess that the old default profile was current, and this was kept during the package upgrade, meaning the profile parts of your steps 3 and 5 weren't needed.
- While I was trying to sort this out, I had MinimWatch reporting an auto-named instance of the server, while the config web page was showing my chosen server name. This resolved itself at some point, not sure why they were different and then the same... this had me searching for multi instances, etc for a while.

Thanks again for the help.

[simoncn]

Exporting a profile is like downloading it as a text file to some external location (not part of your MinimServer installation). Importing a profile is like uploading the profile name and contents from a text file in some external location (not part of your MinimServer installation).

There have been issues with the configuration web pages for profiles caused by outdated cache entries in the web browser. This might be why you are unable to view the contents of your profiles. Try clearing browser cache entries for the device running MinimServer to see if this improves things.

To activate a profile, use, the Select tab.

If the server name reported by MinimWatch is out of sync with your current configuration setting for this name, you need to close the server from MinimWatch and then relaunch it. If the server is running in a container, you can stop and restart the container.

[jamief]

Verified for the clearing the cache to make the profiles work. With it not working, the button text was greyed. I cleared the cache, the button is now active when a profile is selected, and in the case of Export, the browser now downloads the file.