-
Notifications
You must be signed in to change notification settings - Fork 756
Closed
Description
Running any of the noble containers (Such as Tag 11.0.11-jdk25-temurin-noble) is always failing to run in kubernetes and on my podman server where FIPS is enabled.
The older Jammy container tags seem to still work.
...
4-Oct-2025 15:46:03.069 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded Apache Tomcat Native library [2.0.9] using APR version [1.7.2].
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007fbfadee7234, pid=1, tid=5
#
# JRE version: OpenJDK Runtime Environment Temurin-25+36 (25.0+36) (build 25+36-LTS)
# Java VM: OpenJDK 64-Bit Server VM Temurin-25+36 (25+36-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-amd64)
# Problematic frame:
# C [libcrypto.so.3+0x1fd234] EVP_MD_get0_provider+0x4
#
# Core dump will be written. Default location: Core dumps may be processed with "/bin/false" (or dumping to /usr/local/tomcat/core.1)
#
# An error report file with more information is saved as:
# /usr/local/tomcat/hs_err_pid1.log
#
# If you would like to submit a bug report, please visit:
# https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
[error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x00007fbfe245d9a2]
Which can be specifically seen with # C [libcrypto.so.3+0x1fd234] ...
Metadata
Metadata
Assignees
Labels
No labels