/etc/systemd/system.conf:1: Assignment outside of section. Ignoring.

[adelton]

The Fedora images now report

[...]
changed ownership of '/data/etc/systemd/system/systemd-logind.service' from root:root to nobody:nobody
changed ownership of '/data/etc/systemd/system/rpc-gssd.service' from root:root to nobody:nobody
/etc/systemd/system.conf:1: Assignment outside of section. Ignoring.
systemd 255.16-1.fc40 running in system mode (+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP -GCRYPT +GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN -IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 +PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD +BPF_FRAMEWORK +XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
Detected virtualization podman.
Detected architecture x86-64.
[...]

when started like

$ podman run --rm -ti -h ipa.example.test quay.io/freeipa/freeipa-server:fedora-41

The issue seems caused by a change https://src.fedoraproject.org/rpms/systemd/c/29eb35530b29232eed65718d0cd96d67cd7ffd6b.

We added that

# Establish reasonably low open files limit in the container
RUN echo "DefaultLimitNOFILE=1024" >> /etc/systemd/system.conf

in 3d8437d.

We might want to update our Dockerfiles, to avoid the warning message and to set the limits again.

It is also possible that the limits are no longer needed -- that might be also nice to investigate.