| Summary: | JBoss EAP S2I images uses /usr/local rather than /usr/libexec | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Kenjiro Nakayama <knakayam> |
| Component: | ImageStreams | Assignee: | kconner |
| Status: | CLOSED UPSTREAM | QA Contact: | Tomas Schlosser <tschloss> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.1.0 | CC: | agoldste, aos-bugs, bparees, haowang, jokerman, mmccomas |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: |
undefined
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-02-20 15:14:53 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Kenjiro Nakayama
2016-03-25 11:09:57 UTC
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. |