On Wed, 2018-03-07 at 08:52 +0100, Alberto García Sola wrote: > Reading the documentation I find little or none information regarding > containers and Docker, but I've found a few comments in the changelog > regarding Docker. I plan to use them in a highly scalable and elastic > environment. > I wonder, what's the best way to containerize 389DS using Docker to > use in production systems? > Any considerations regarding storage (beyond being persistent)? > Any experiences using Docker and 389DS in production systems? Hi there, I'm currently working on docker support in 389-ds. The current status is "almost there", but before I approve it for use I have a high standard I want to meet. I want our support to be the best possible. I want to be able to redefine root password via envariables, and I want to be able to configure the server via environment or some other means that would work nicely in something like kubernetes so you can then have scripted scaling for replicas. We also have some plans for inplace upgrades (rather than the perl scripts) so that containers can upgrade at run time rather than relying on rpm/deb to run upgrade scripts. Today, you can run ds in a container, but you need to build the /etc/dirsrv/slapd-<instance> directory "seperately" and then bring that to the container. If you are interested in testing the current image, I can provide steps on using it, and if you have some use cases or ideas, I'd love to hear them. I really want our docker support ready in the next few months. Thanks! > Regards, > Alberto. > _______________________________________________ > 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to 389-users-leave@lists.fedoraproject.o > rg -- Thanks, William Brown _______________________________________________ 389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
