Thursday, September 1, 2022

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

On Thu, Sep 1, 2022 at 2:34 PM Ronald Wimmer <> wrote:
On 01.09.22 14:23, Viktor Ashirov wrote:
> On Thu, Sep 1, 2022 at 2:05 PM Ronald Wimmer <> wrote:
>> On 01.09.22 13:41, Viktor Ashirov wrote:
>>> 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
> What is the image that you're using?
> $ podman run -ti rpm -q 389-ds-base
> 389-ds-base-2.0.16-1.fc35.x86_64

There is no 389-ds-base package installed but I can find a package named
docker run -ti rpm -q 389-ds
This is a bit unexpected.
We have images based on 
I filed an issue to fix this split.

Looks like you have an image based on openSUSE, even though you specify the full registry in the image path, and it should pull an image based on Fedora.
By default these images run as different users:
$ podman run -ti whoami

$ podman run -ti whoami

And the configuration that is described in the guide is using the image from so that it can be run unprivileged and rootless.
So could you please ensure that you run the image from


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