On Thu, Sep 1, 2022 at 2:34 PM Ronald Wimmer <ronaldw(a)ronzo.at> wrote:
On 01.09.22 14:23, Viktor Ashirov wrote:
> On Thu, Sep 1, 2022 at 2:05 PM Ronald Wimmer <ronaldw(a)ronzo.at> wrote:
>
>> On 01.09.22 13:41, Viktor Ashirov wrote:
>>> On Thu, Sep 1, 2022 at 1:24 PM Ronald Wimmer <ronaldw(a)ronzo.at>
wrote:
>>>
>>>> We stuck to the guide on
>>>>
>>
https://directory.fedoraproject.org/docs/389ds/howto/howto-deploy-389ds-o...
>>>> 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 quay.io/389ds/dirsrv 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
389-ds:
docker run -ti quay.io/389ds/dirsrv:latest rpm -q 389-ds
389-ds-2.2.2~git11.f002e9e09-150.3.x86_64
This is a bit unexpected.
We have images based on
openSUSE:
https://hub.docker.com/r/389ds/dirsrv
Fedora/CentOS Stream:
https://quay.io/repository/389ds/dirsrv
I filed an issue
https://github.com/389ds/389-ds-base/issues/5436 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 docker.io/389ds/dirsrv whoami
root
$ podman run -ti quay.io/389ds/dirsrv whoami
dirsrv
And the configuration that is described in the guide is using the image
from quay.io/389ds/dirsrv so that it can be run unprivileged and rootless.
So could you please ensure that you run the image from quay.io/389ds/dirsrv
?
Thanks.
_______________________________________________
--
Viktor