Hide Forgot
Description of problem: - JBoss EAP s2i images use /usr/local rather than /usr/libexec - It should use /usr/libexec according to https://github.com/openshift/source-to-image/pull/370 Version-Release number of selected component (if applicable): - v3.1.1.6-21-gcd70c35 - Current eap64-openshift:latest image as below - registry.access.redhat.com/jboss-eap-6/eap64-openshift 1.1 dfdbff449ef7 3 months ago 1.156 GB How reproducible: Steps to Reproduce: 1. Run s2i image by eap builder image 2. Check the build log Actual results: ~~~ I0324 07:56:05.272051 1 download.go:57] Using image internal scripts from: image:///usr/local/s2i/assemble I0324 07:56:05.272067 1 download.go:57] Using image internal scripts from: image:///usr/local/s2i/run ~~~ Expected results: ~~~ I0325 10:19:32.121987 1 download.go:57] Using image internal scripts from: image:///usr/libexec/s2i/assemble I0325 10:19:32.122041 1 download.go:57] Using image internal scripts from: image:///usr/libexec/s2i/run ~~~ Additional info: - I wanted to send a patch by myself. But it is CLOSED source!!
The image contains "io.openshift.s2i.scripts-url" to setting the s2i script location which override the default location "/usr/libexec/s2i". [root@openshift-209 ~]# docker inspect registry.access.redhat.com/jboss-eap-6/eap64-openshift |grep io.openshift.s2i.scripts-url "io.openshift.s2i.scripts-url": "image:///usr/local/s2i", openshift build support custom script location,so I don't think it's a build related bug ,change to component image. Not sure whether xpass image team will update image to use the default s2i location.
@kenjiro You can certainly send a patch for this, it would be welcome On the face of things this seems to be a minor, relatively recent change that has no functional impact other than to align with a different directory structure. This would be a low priority for us however we should be able to schedule it at some point. The image you are referring to is certainly not the latest version so not sure where you are getting that information from, there have been numerous 1.2 images released and now a 1.3 image.
Logged the associated issue as an optional enhancement.
closing as this is being tracked in JIRA now, which is the mechanism for middleware image issues.