MinimServer 2 in Docker - best approach for persistent config?

[kennurnes]

(01-08-2021 22:15)simoncn Wrote:  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:

Thanks for the response and I might be unclear with what I meant with that I'm running a Docker server which means in my case a dedicated Ubuntu Docker service and not using any NAS docker implementation (actually went away from this since the containers that I've deployed prevented to disks to spin down.).

Suggestion would be to make use of /config volume (-v /opt/minimserver/config:/config) for MinimServer when deployed in Docker environment which isn't been used now. Noticed that the config directory setup is empty; if used that would make the automatic deployment far easier (configuration would be kept) and together being able to pull the 'Latest' which throws an error when used and one have to specify which version to deploy. So on my Wish List I have these two tweaks which would make the docker deployment far easier.