Open jmtd opened 5 years ago
Ultimately we can probably delete those two lines from the s2i/run script.
same issue with openjdk/openjdk-11-rhel8 but not openjdk/openjdk-11-rhel7 or redhat-openjdk-18/openjdk18-openshift:1.6
In the working image, /opt/jboss/container/maven/default/scl-enable-maven -> /opt/jboss/container/maven/35/scl-enable-maven
This is the line that creates the symlink:
jboss/container/maven/default/bash/configure.sh:ln -s /opt/jboss/container/maven/35/* /opt/jboss/container/maven/default
There's a few things wrong there. It's 35-specific so will fail for 36 amongst other things. There directory is created by the 35scl module when copying in the single file scl-enable-maven
which the 35 module doesn't have so doesn't copy and so doesn't create the directory.
FYI: The error /usr/local/s2i/run: line 15: /opt/jboss/container/maven/default//scl-enable-maven: No such file or directory
also occurs in UBI images registry.access.redhat.com/ubi8/openjdk-11:latest
and registry.access.redhat.com/ubi8/openjdk-8:latest
.
A simple RUN touch /opt/jboss/container/maven/default/scl-enable-maven
in the Dockerfile let's the error disappear. Hope there are no side-effects ;-)
A simple RUN touch /opt/jboss/container/maven/default/scl-enable-maven in the Dockerfile let's the error disappear. Hope there are no side-effects ;-)
That should be fine. I think we fixed this a while ago in our development branch but we haven't made a release since. (Soon!)
With the OpenJDK RHEL8/JDK11 image, on start up, one gets the following error
The image uses the following modules at the top level (image):
Cekit (3.4.0) unravels this to the following full list
the script
jboss/container/java/s2i/bash/artifacts/usr/local/s2i/run
contains the following(that comment looks suspicious)
the var JBOSS_CONTAINER_MAVEN_DEFAULT_MODULE is not set in that script. It's defined as set in
jboss/container/maven/default/bash/module.yaml
, so it's set by the build process (in the Dockerfile) to/opt/jboss/container/maven/default/
.