MinimServer 2 in Docker - best approach for persistent config?

[mr_smidge]

(30-12-2020 20:41)simoncn Wrote:  Moving the data directory to a volume will not enable you to destroy and recreate a container (compose down/up) while preserving your previous license activation. To avoid "orphaned" license activations, you will need to deactivate the license before destroying the container and reactivate it in the new container. Alternatively, you can stop and start the container (compose stop/start) instead of destroying it.

The scenario that comes to mind is an upgrade to the version of the minimserver2 Docker image, which would entail a rebuild of the container (please correct me if wrong) - in this case, does an admin need to de-activate/re-activate a license before upgrading?

Thanks!