Jib: respect JAVA_OPTIONS env var in entrypoint

[rvansa]

Description
Containers created using container-image-jib should respect env var JAVA_OPTIONS set for the container.

Implementation ideas
"Standard" base images for Java have some sort of run-java.sh script that counsel JAVA_OPTIONS and pass these to the JVM. Jib does only use java $(quarkus.jib.jvm-arguments) -jar quarkus-run.jar where quarkus.jib.jvm-arguments is set at build time. That limits the options to use the entrypoint as-is.

[quarkusbot]

/cc @geoand

[geoand]

Interesting, thanks!

Do you have an example run-java.sh script?

[rvansa]

@geoand Actually the default base image quarkus.jib.base-jvm-image -> fabric8/java-alpine-openjdk11-jre contains /deployment/run-java.sh - this requires JAVA_APP_JAR env var though and does more. In my simplistic case it was enough to add

#!/bin/sh

if [ -z "$JAVA_OPTIONS" ]; then
  JAVA_OPTIONS="-Djava.util.logging.manager=org.jboss.logmanager.LogManager"
fi

java $JAVA_OPTIONS -jar quarkus-run.jar
``

[rvansa]

Also what's the recommended way to add such custom entrypoint script? I have created a base image since I wanted to install jq to the image and add some additional files, but it seems that it's not possible to easily add files via quarkus.container-image.*

[geoand]

Right!

What you want is basically covered by #10011 and #10071.

We haven't documented this feature as it's basically the same as what Jib proper offers, but I am thinking that we probably should...
Would you be willing to contribute that improvement?

[geoand]

What I mentioned above is actually part of the documentation now, so I'll close this