Hi! I read through all related issues in freeipa-container and actually saw that. You are right, I was trying to run a container with cap_add: ALL. But otherwise gssproxy service inside the container is failing with the error:
>gssproxy[4059]: [2023/07/15 15:32:06]: Failed to apply capability set: >[1:Operation not permitted] gssproxy version: >[root@ipamaster /]# rpm -qa | grep gssproxy >gssproxy-0.8.4-alt1.x86_64 Anyways, when I set cap_add: ALL and service actually starting inside the container it feels like the interaction is lacking the problem persist around gssproxy. What I did is I download the actual OS version that corresponds to the container version so the package versions are the same. I noticed (with debug_level = 2 of gssproxy.conf) that during the install process after initialization of gssproxy server with healthy install on the standalone OS you can see journald logs, that shows that interaction via gssproxy is healty. However at the same step during container install (when cap_add: ALL and gssproxy service is starting) there are no logs, which suggest that something is still wrong I guess. _______________________________________________ FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
