Until jlink-dev is merged, it's easy to forget that the incoming ImageStream to Stage 1 needs to have the jlink integration scripts in them.

Assuming you have a local builder image from the jlink-dev branch, it's possible to manually push that into an imageStream in OpenShift. something like:

REGISTRY_AUTH_PREFERENCE=docker oc registry login
docker tag ubi9/openjdk-17:1.18 default-route-openshift-image-registry.apps-crc.testing/jlink1/ubi9-openjdk-17:1.18
docker push default-route-openshift-image-registry.apps-crc.testing/jlink1/ubi9-openjdk-17:1.18

However, to catch the situation where the imageStream does not have the jlink scripts early, I think we should extend the stage 1 Dockerfile to perform a check for one of the jlink scripts (e.g. opt/jboss/container/java/jlink/preflight.sh) and fail the build if it isn't present. Nothing more complex than RUN test -f ... I think.