Hide Forgot
.NET Core 1.1 docker images support using the s2i tool. The s2i tool, part of source-to-image RPM, is not shipped with .NET Core. Without shipping the s2i tool in our repository, OpenShift can still use .NET Core docker files, but anyone who tries to use s2i manually will hit a wall and not be able to build container images using source. There are are few options on how to get source-to-image: 1. Customers can get it from RHSCL. This is not ideal because .NET Core should be stand alone and not dependent on RHSCL. 2. Customers can get it from Github. We would like to avoid this because part of our value proposition is that we build, package and maintain software and resolve issues as they happen. None of them is good enough. We should include source-to-image in the .NET Core channel.
How do our distributions of OpenJDK deal with this?
As far as I know, we never shipped an OpenJDK docker image. The bug for docker image for OpenJDK [1] is marked as verfied, but contains a note that it was not shipped. The erratum [2] (last updated a week ago) agrees: "Per Deepak Bhole: We still have no resolution. Let's close it for now then and we will re-open it when we're ready." [1] https://bugzilla.redhat.com/show_bug.cgi?id=1318209 [2] https://errata.devel.redhat.com/advisory/24535
Verified, We can see source-to-image-1.0.9-1.el7 in 7Server-dotNET-1.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2826.html