This is a self deploying container for running a Univention Corporate Server (UCS) with the role of primary, backup, replica directory node or managed node.
Build your own bootstrap container image ( optionally )
If you like, you can build your own minbase container image from scratch. You find a script called bootstrap.sh, this works for docker or podman.
docker search univention/univention-corporate-serverThere are four options to deploy, it's recommended to study the examples too.
This section will explaine the container environment with the minimum and/or maximum amount settings.
Here you will find all basic examples for running a ucs with different systems roles.
Here you will find advanced example(s) for running a ucs with different systems roles and some additional options, like networking and external certificate(s).
Build your own minbase container image from scratch and directly from testing repository ( updates-test.software-univention.de ) to your local container registry.
Would you like to expand the project for yourself? Have a look at the section extended usage and read about the possibilities with a template file and how to place it. But if you think, that will be great for all of us, check this on too.
You don't wan't sensitive credentials in your environment variables after an succeeded first start/boot, take a look into this section to cleanup your container.
Please read the contributing guide to find more information about the UCS development process, how to propose bugfixes and improvements. The Code of Conduct contains guidelines we expect project participants to adhere to.
Univention Corporate Server is built on top of many existing open source projects which use their own licenses. The source code of all parts written by Univention like the management system is licensed under the AGPLv3 if not stated otherwise directly in the source code. Please see the license file for more information.