Chapter 5. Known issues

The quarkus-container-image-s2 extension, which is typically used indirectly through the quarkus-openshift extension, treats the Red Hat OpenJ9 images recommended for s390x architecture as if they do not include the run-java.sh script. This affects the generated openshift.yml file.

If the image uses the run-java.sh script, the container definition only includes several environment variables. It does not include a command that should be executed in the container. Instead, the default S2I run script is used which executes the run-java.sh script.

If the image does not use the run-java.sh script, the container definition includes the java command that should be executed in the container.

One difference between these scenarios is that the run-java.sh script changes the current working directory to the directory where the application JAR file is located, typically /deployments. This is important when mounting a ConfigMap with the application.properties configuration file into the container filesystem. With the run-java.sh script, the ConfigMap typically must be mounted into the /deployments/config directory, while with the other images, the ConfigMap must be mounted into the default working directory defined by the image.