MinimServer 2 in Docker - best approach for persistent config?

[mr_smidge]

Hi Simon,

(28-12-2020 17:18)simoncn Wrote:  If you destroy the container and recreate it, this would cause the settings in /opt/minimserver/data to be lost.

This is exactly what happened - I recreated the container (via compose down/up) and data stored internally within the container was lost.

Quote:I think your solution would work for preserving the MinimServer settings when the container is destroyed and recreated. This is not a supported and tested configuration and I cannot guarantee that it will work correctly in all cases.

So far no issues, so I will keep my fingers crossed. I'm happy with the current workaround, as I want data to be safe if the container is recreated, but it's worth noting that some people advise not storing config/logging within containers:

https://developers.redhat.com/blog/2016/...ontainers/

As MinimServer is now working for me, I don't have a strong opinion on the above.

Quote:You are likely to have problems if the data directory is used by more than one container at the same time. If you don't do this, the presence of log and pid files should not be a problem.

Absolutely - I do not intend to share the data directory beyond just the running instance.

Quote:You might find that a full license activation created with the original container no longer works if you destroy and recreate the container. Have you tried this?

...

Please use the contact form on this page to request a license reset. Please provide your license code in the Message field.

Exactly this - the license activation had disappeared upon recreating the container. After moving the data directory to a volume, I activated again, but showed 2 activations had been made.

Request now sent to reset - many thanks.