Description of problem: In the container image registry.redhat.io/rhpam-7/rhpam-kieserver-rhel8, there is a symbolic link at /usr/local/s2i/scl-enable-maven that points to /opt/jboss/container/maven/default/scl-enable-maven. [jboss@6b70467d8f9b ~]$ ls -l /usr/local/s2i/scl-enable-maven lrwxrwxrwx. 1 jboss root 51 Jan 29 11:20 /usr/local/s2i/scl-enable-maven -> /opt/jboss/container/maven/default/scl-enable-maven However, listing the contents of that directory shows: [jboss@6b70467d8f9b ~]$ ls /opt/jboss/container/maven/default/ '*' jboss-settings.xml maven.sh The symlink is therefore invalid and attempting to execute results in failure. Version-Release number of selected component (if applicable): - latest - 7.6.0-2.1580292314 - 7.6.0-2 - (Possibly more ?) How reproducible: Steps to Reproduce: 1. docker run -it --rm registry.redhat.io/rhpam-7/rhpam-kieserver-rhel8:7.6.0-2.1580292314 /bin/bash 2. [jboss@6b70467d8f9b ~]$ /usr/local/s2i/scl-enable-maven Actual results: bash: /usr/local/s2i/scl-enable-maven: No such file or directory Expected results: scl-enable-maven should be executed Additional info:
It seems like the image comes with maven pre-enabled, so sourcing /usr/local/s2i/scl-enable-maven would not be necessary as it was in previous versions. But if that is the case, the broken symlink should still be removed.
I don't think this is the right product or even the right issue tracker. As best I can see that's the JIRA RHPAM board. I relayed this bug there: https://issues.redhat.com/browse/RHPAM-2855 Please pursue this issue there.