> On 6 Jan 2022, at 08:49, Steve F <firstname.lastname@example.org> wrote:
> I am in the process of building my own container containing ds-389, using this docker file as the initial guidance -> https://build.opensuse.org/package/view_file/home:firstyear/389-ds-container/Dockerfile?expand=1 (and using /usr/lib/dirsrv/dscontainer to bootstrap the image and bring up the container)
> I am having a think about the upgrade process for this instance. If I am storing the schema/relevant files on persistent storage, will /usr/lib/dirsrv/dscontainer be smart enough to upgrade the backend on startup if I have built a new container with a new version of ds-389? In the past, I beleive the installer RPM's were running perl/python scripts to perform backend updates.
> I THINK it is, but I can't find anything definitive.
Yes, it is smart enough to upgrade on startup. Provided you mount your persistent storage in the same location, it will do all the upgrading for you :)
It's actually the dirsrv binary itself that does the upgrade, dscontainer just knows how to launch it.
Hope that helps!
> Any help is appriciated.
> 389-users mailing list -- email@example.com
> To unsubscribe send an email to firstname.lastname@example.org
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://email@example.com
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Senior Software Engineer, Identity and Access Management
SUSE Labs, Australia
389-users mailing list -- firstname.lastname@example.org
To unsubscribe send an email to email@example.com
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://firstname.lastname@example.org
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure