Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
OpenJ9 images not recognized as using run-java.sh
See original GitHub issueDescription
Quarkus has a hard-coded list of base S2I images known to use the run-java.sh mechanism: https://github.com/quarkusio/quarkus/blob/1.5.1.Final/extensions/container-image/container-image-s2i/deployment/src/main/java/io/quarkus/container/image/s2i/deployment/S2iBaseJavaImage.java#L11-L19
This list doesn’t include the Red Hat OpenJ9 images, which makes for a sub-par experience.
Implementation ideas
Just add the known OpenJ9 images to the S2iBaseJavaImage enum:
- https://catalog.redhat.com/software/containers/openj9/openj9-8-rhel7/5ddfdbf75a13461646f8171a
- https://catalog.redhat.com/software/containers/openj9/openj9-11-rhel7/5ddfdb26dd19c71643b652d5
- https://catalog.redhat.com/software/containers/openj9/openj9-8-rhel8/5ddfdbb8bed8bd164a0b1fa1
- https://catalog.redhat.com/software/containers/openj9/openj9-11-rhel8/5ddfdb765a13461646f816f0
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
That’s how I understand it, so feel free to take it and ping me and @Ladicek on the PR 😃
@iocanel if you can do it that would be great. Otherwise I’ll squize it in tomorrow