The "Using jlink to customize Java runtime environment" documentation  on OpenJDK (11|17|21) section 2:

OpenJDK 11: https://access.redhat.com/documentation/en-us/red_hat_build_of_openjdk/11/html/using_jlink_to_customize_java_runtime_environment/creating-custom-jre

OpenJDK 21: https://access.redhat.com/documentation/en-us/red_hat_build_of_openjdk/21/html/using_jlink_to_customize_java_runtime_environment/creating-custom-jre

OpenJDK 17: https://access.redhat.com/documentation/en-us/red_hat_build_of_openjdk/17/html-single/using_jlink_to_customize_java_runtime_environment/index

~~~

For best results, use portable Red Hat binaries as a basis for a Jlink runtime, because these binaries contain bundled libraries.

~~~

Change to the following:

~~~

For best results, create the custom JRE from a JDK distribution that is best aligned with the deployment environment: rpm, container, or portable build. For example, you would want to use an rpm or container if your deployment leverages RHEL integration points: crypto polices (e.g FIPS), timezone information, global cacerts.

~~~