Hi, It appears to be that jlink-produced custom images rely on the fact that jmods in the module-path have been produced with static linking and bundled libraries. This assumption might not always hold for downstream builders.
Since JDK 9+ there are build options to use system lcms, system jpeg, system gif libs etc. Example: $ bash configure [...]--with-libpng=system If a build was produced in such a way, the resulting image would then depend on a similar (if not same) system libpng than the host on which the original JDK - used for the module-path - has been built. Some background info is here: https://bugzilla.redhat.com/show_bug.cgi?id=1659192 Has this been considered at all? Am I wrong in thinking that the canonical answer for this is: Don't build the JDK that way Thanks, Severin
