On pe, 04 marras 2022, Leo O via FreeIPA-users wrote:
Hm, I was just using google, I thought it will point me to the official
documentation if there is something but it didn't. So I thought,
nothing about that (maybe my search phrases were just weak). But good
to know, thank you very much for the link.

1. The build seems to be working, at least my docker container with my
extension behaves the same as the official rocky-9-4.9.8 docker. Both
throw the same errors, any ideas on that?
https://github.com/freeipa/freeipa-container/issues/488

I left my comment there. In short, you are configuring container to
control time on the host which is almost never a good idea. Use
'--no-ntp' option to ipa-server-install or see
https://pagure.io/freeipa/issue/8316.

2. Is the "old" docker "rocky-8-4.9.8" deprecated? Haven't been an
update in the last 7 days whereas "rocky-9-4.9.8" has one, two days
ago.

Rocky 8 distribution itself tracks CentOS 8 Stream. Rocky 9 tracks
CentOS 9 Stream. These are two different distribution releases, with
different package build cadencies. Neither one is under any control of
freeipa-container project.

The whole container build process is pretty much automated with
scheduled runs by Github Actions CI and is using packages provided by the
specific distributions. If the build succeeded, tests passed, and the
image actually differs from the previously uploaded one, the image gets
uploaded to the container registries.

--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
_______________________________________________
FreeIPA-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to