MinimServer 2 in Docker - best approach for persistent config?

[simoncn]

You can install an online update (such as the latest update 195) in an existing container without losing any configuration settings or needing to do a full scan of your library.

If the update is an automatic update (such as the latest update 195), you can install it by restarting MinimServer using MinimWatch (select the Restart action). You should also be able to install the update by stopping and starting the Docker container for MinimServer. You should not create a new Docker container.

If you are updating to a new version (such as 2.0.18), the simplest way to update to the new version is to create a new container for the new version. This causes you to lose your license activation and your current configuration and requires a full scan of your library. You can avoid these issues by updating MinimServer within the existing Docker container. For example, to update from MinimServer 2.0.16 to MinimServer 2.0.18 in a Docker container running on an QNAP Intel NAS, do the following:

1) From the Downloads page, download the MinimServer Linux package for the new version to a computer. For an Intel NAS, this package is minimserver-2.0.18-linux-intel.tar.gz.

2) Copy this file to the MinimServer/opt shared folder on the NAS

3) In the MinimServer Docker container, run this command:
/opt/minimserver/bin/update /MinimServer/opt/minimserver-2.0.18-linux-intel.tar.gz

4) This should produce the following messages:
/opt/minimserver/minimserver-2.0.16/bin/stopall: line 23: ps: command not found
No MinimServer instances are running
MinimServer update completed successfully

5) From Container Station, stop and restart the Docker container

6) The Docker container should now be running the updated version of MinimServer with no loss of configuration settings or the existing license activation and no need for a full rescan.