This issue arises because the container is running on top of a FIPS- enabled kernel which provides the /proc/sys/crypto/fips_enabled = 1 flag.
On Noble, openssl sees this flag and expects therefore to be operating in FIPS mode, but at this point the Noble container is not in FIPS mode - we haven't finished developing the FIPS components and haven't released them - and the result is that it throws some errors. The workaround is to either not run the container on a FIPS-enabled kernel; or to set the environment variable in the Noble container to disable FIPS mode: ENV OPENSSL_FORCE_FIPS_MODE=0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066990 Title: high memory consumption in Ubuntu Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/2066990/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs