Hello, I could use a little advice before I go down too many more rabbit holes: We are looking to run 389 in Docker and we prefer a stable version that will be supported for a while. We have a large user base and and value stability over new features. Is there a maintained docker image for, ideally, 389 versions 2.6 or 2.7? I'm open to 2.8 or 3.0 but worry they are a bit too bleeding edge for use in a large-ish environment. 2.4 worked well for us when we last tested but looks to now but deprecated. I'm happy to diy but from my testing and reading 2.6 and 2.7 dscontainer, at least in Alma Linux 9 as the base Docker image, seem to be buggy: the config directory is not correctly populated in the data directory. I am game for diy'ing a 2.8 or 3.0 Docker image if the consensus is that they are production ready but does dscontainer work in them and do you have a suggestion for what Docker operating system base image to use? I see 3.0, and maybe 2.8, can be enabled through copr in Alma 9 but don't want to get *too* exotic for production use. thank you! -morgan -- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.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.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Monday, May 18, 2026
[Test-Announce] Heroes of Fedora Quality for Fedora 44
-- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.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.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Sunday, May 17, 2026
Self-Introduction: archer69m-i-a (French)
Hello everyone, I'm Kevin, nice to meet you. Bonjour depuis la France, et enchanté! My FAS username is archer69m-i-a (since I couldn't use an underscore during creation), but my usual FOSS username is Archer_M-I-A. I'm a French Fedora user interested in French l10n topics. # Interests in Fedora contribution ? As a Fedora user with recent interests in open-source projects, I wanted to get behind the scene to understand how it works. # Interests in Translations contributions ? Since I'm not a developer, it's the easiest way for me to contribute and improve my skills on interesting projects. I get to learn a lot of things beyond just improving my vocabulary, and this is motivating to know that more French-speaking people can gain access to open-source tools. # Native language and additional languages? Mother tongue is French and fluent in English. # Involved in other things in Fedora? Currently no # Any experience with open-source or online communities? A recent contribution to GNOME French l10n as a Fedora GNOME user. This confirms my interest in putting efforts in French l10n activities beyond just GNOME. # Parts of L10n/G11n/Translation project that are interesting to me? I think that documentation translation is a good entry point, as it gives you a broad vision of the main features of a software/process. UI translation is also interesting, but I didn't get to do much on this side. Besides, discovering new tools and processes that enable translation is always nice. # Time dedicated to FOSS I think I can dedicate a few hours a week to FOSS, mainly on the weekend. But I am currently experimenting with my schedule to find the perfect balance between work, personal life and FOSS activities, in order not be overwhelmed by everything. So I may proceed with baby steps at the beginning. Have a nice day, everyone! -- _______________________________________________ trans mailing list -- trans@lists.fedoraproject.org To unsubscribe send an email to trans-leave@lists.fedoraproject.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.fedoraproject.org/archives/list/trans@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Thursday, May 14, 2026
[Test-Announce] Fedora-IoT 45 RC 20260514.0 nightly compose nominated for testing
Announcing the creation of a new nightly release validation test event for Fedora-IoT 45 RC 20260514.0. Please help run some tests for this nightly compose if you have time. For more information on nightly release validation testing, see: https://fedoraproject.org/wiki/QA:Release_validation_test_plan Test coverage information for the current release can be seen at: https://openqa.fedoraproject.org/testcase_stats/45iot You can see all results, find testing instructions and image download locations, and enter results on the Summary page: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_45_RC_20260514.0_Summary The individual test result pages are: https://fedoraproject.org/wiki/Test_Results:Fedora-IoT_45_RC_20260514.0_General Thank you for testing! -- Mail generated by relvalconsumer: https://forge.fedoraproject.org/quality/relvalconsumer -- _______________________________________________ test-announce mailing list -- test-announce@lists.fedoraproject.org To unsubscribe send an email to test-announce-leave@lists.fedoraproject.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.fedoraproject.org/archives/list/test-announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
Wednesday, May 13, 2026
[389-users] Re: Cannot change nsslapd-db-max-locks
On 5/13/26 4:03 PM, Orion Poplawski via 389-users wrote: > On 5/13/26 13:44, Mark Reynolds wrote: >> On 5/13/26 3:32 PM, Orion Poplawski via 389-users wrote: >>> So it seems that something is messed up with this particular host. >> The "db locks" are stored under /dev/shm/slapd-INSTANCE/ Perhaps there is >> not a lot of space allocated for /dev/shm on that host? > This is what it had: > > Filesystem Size Used Avail Use% Mounted on > tmpfs 1.5G 257M 1.3G 17% /dev/shm > > I bumped it a bit: > > Filesystem Size Used Avail Use% Mounted on > tmpfs 1.8G 289M 1.5G 17% /dev/shm > > Now I'm starting to think that I'm looking at two different things as the > nsslapd-db-max-locks is increasing after boot: > > nsslapd-db-current-locks: 52 > nsslapd-db-max-locks: 72 > > nsslapd-db-current-locks: 99 > nsslapd-db-max-locks: 174 > > nsslapd-db-current-locks: 101 > nsslapd-db-max-locks: 178 > > So maybe the reason I see a large value on one machine is more indicative that > something went haywire on it making it hit the configured maximum. Not sure, I know that the monitor stats you are looking at come directly from libdb and not the core server - so it's kind of a black box. It would require debugging libdb to see why it's behaving this way. > > > > -- Identity Management Development Team -- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.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.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
F44 election nominations now open
--
TZ=America/Atlanta (UTC-4) 🕗
While I may be sending this email outside my normal office hours, I have no expectation to receive a reply outside yours.
-- _______________________________________________ announce mailing list -- announce@lists.fedoraproject.org To unsubscribe send an email to announce-leave@lists.fedoraproject.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.fedoraproject.org/archives/list/announce@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
[389-users] Re: Cannot change nsslapd-db-max-locks
On 5/13/26 13:44, Mark Reynolds wrote: > > On 5/13/26 3:32 PM, Orion Poplawski via 389-users wrote: >> So it seems that something is messed up with this particular host. > The "db locks" are stored under /dev/shm/slapd-INSTANCE/ Perhaps there is > not a lot of space allocated for /dev/shm on that host? This is what it had: Filesystem Size Used Avail Use% Mounted on tmpfs 1.5G 257M 1.3G 17% /dev/shm I bumped it a bit: Filesystem Size Used Avail Use% Mounted on tmpfs 1.8G 289M 1.5G 17% /dev/shm Now I'm starting to think that I'm looking at two different things as the nsslapd-db-max-locks is increasing after boot: nsslapd-db-current-locks: 52 nsslapd-db-max-locks: 72 nsslapd-db-current-locks: 99 nsslapd-db-max-locks: 174 nsslapd-db-current-locks: 101 nsslapd-db-max-locks: 178 So maybe the reason I see a large value on one machine is more indicative that something went haywire on it making it hit the configured maximum. -- Orion Poplawski he/him/his - surely the least important thing about me Manager of IT Systems 720-772-5637 NWRA, Boulder Office FAX: 303-415-9702 3380 Mitchell Lane orion@nwra.com Boulder, CO 80301 https://www.nwra.com/
-- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-leave@lists.fedoraproject.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.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new