external tests are unable to test "some" jdks

The external tests are runnign by default in container, and are mounting jdk inside. If the jdk is not exactly standalone (quite common is symlink to system tzdata and cacerts) then the jdk can not be tested

In my case, the "some" means jdks with symlink to keystore, which when mounted is not resolved, and thus jdk fails to even print hello world.

Any thoughts on this?

The only one I have is to add option, that such jdk will not be mounted, but copied in, with all symlinks resolved during copy....

Another - better, but not that srigtforward solution may be to scan the future "/opt/java/openjdk/" in runtime, and try to copy-in missing resources.
Another one may be to overwrite the known symlinked locations by -DcacertLocation -Dkeystore .. This is nicely moving it to user space, But afaik there is none -D for tzdata.

No file or test entry point is named. Start by reproducing an external test in the container with a JDK whose keystore or tzdata is symlinked, then inspect how the JDK is mounted and accessed; done means the affected JDK can run a basic “hello world” test successfully.

Written by the indexing model from the issue text.