Thursday, September 1, 2022

[389-users] Re: 389DS on K8s - dirserv won't start

On Thu, Sep 1, 2022 at 1:24 PM Ronald Wimmer <> wrote:
We stuck to the guide on but tried to leave out LDAPs and all the certificate stuff for now. Pod is starting but crashes immediately with the following error:

kubectl logs dirsrv-0 dirsrv-container -n dirsrv-dev
INFO: The 389 Directory Server Container Bootstrap
INFO: Inspired by works of: ITS, The University of Adelaide
INFO: 389 Directory Server Version: 2.2.2
INFO: Initialising 389-ds-container due to empty volume ...
DEBUG: Running setup with verbose
DEBUG: START: Starting installation ...
DEBUG: READY: Preparing installation for localhost...
INFO: Validate installation settings ...
DEBUG: PASSED: using config settings 999999999
DEBUG: PASSED: user / group checking
DEBUG: PASSED: prefix checking
Traceback (most recent call last):
  File "/usr/lib/dirsrv/dscontainer", line 467, in <module>
  File "/usr/lib/dirsrv/dscontainer", line 270, in begin_magic
    if not sds.create_from_args(g2b.collect(), s2b.collect()):
  File "/usr/lib/python3.10/site-packages/lib389/instance/", line 685, in create_from_args
    self._prepare_ds(general, slapd, backends)
  File "/usr/lib/python3.10/site-packages/lib389/instance/", line 612, in _prepare_ds
    assert_c(len(insts) == 0, "Another instance named '%s' may already exist" % slapd['instance_name'])
  File "/usr/lib/python3.10/site-packages/lib389/", line 1274, in assert_c
    raise AssertionError(msg)
AssertionError: Another instance named 'localhost' may already exist 

Any idea why?
When persistent volume is mounted, dirsrv user doesn't have write access to it. In the guide there is a workaround to run an init container that would chown /data to dirsrv user. Do you have it in your config?


389-users mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:


No comments:

Post a Comment