[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: s2i-base ancestry

https://github.com/sclorg/rhscl-dockerfiles/tree/master/rhel7.s2i-base is the future, so you should go off that, which as you noted generates registry.access.redhat.com/rhscl/s2i-base-rhel7

Some existing s2i rhel images are still based on https://github.com/openshift/s2i-base however.

Note that there's no requirement your s2i image use that base image.  If you find it convenient, great, but its primary purpose is to serve as a common base for the existing suite of SCL-based s2i images, its use as a general base for s2i images is a secondary goal (meaning if it does not serve your purposes, requests for enhancement will be considered in the context of the primary goal).

On Mon, Aug 29, 2016 at 12:11 AM, Dale Bewley <dale bewley net> wrote:

Where does the OpenShift Enterprise s2i-base image come from?

A. https://github.com/openshift/s2i-base or
B. https://github.com/sclorg/rhscl-dockerfiles/tree/master/rhel7.s2i-base

Repo A builds FROM rhel7.2 and seems to create registry.access.redhat.com/openshift3/sti-base
Repo B builds FROM rhel:7.2-released and seems to create registry.access.redhat.com/rhscl/s2i-base-rhel7

I see s2i-python repo has been renamed to https://github.com/sclorg/s2i-python-container
but it doesn't use either. It builds FROM openshift/base-rhel7.

Is there a direct lineage that can be followed? Sclorg seems to own all the s2i now, but at what point do images enter the openshift part of the registry?

What should I model a custom s2i on?


users mailing list
users lists openshift redhat com

Ben Parees | OpenShift

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]