I'm trying to understand best practices for creating and maintaining builder images.
For example, I would like to start with this repo https://github.com/openshift/sti-python/blob/master/2.7/ and customize the Dockerfile to the include the Oracle instantclient libraries. As a test with fewer dependencies I used s2i https://github.com/openshift/source-to-image/releases/ and referred to openshift/sti-php to bootstrap a simple Dockerfile https://gist.github.com/dlbewley/88bce324daf700d49bf0 for creating static-content sites. I then used Docker build strategy `oc new-app http://gitlab/static-builder.git` to create an app from the git repo. OpenShift built the image called `static-builder` (and an app with no real content) in my project. I was able to utilize that with `oc new-app builder-image~http://gitlab/static-site.git`. I like that I can use a web hook to rebuild my builder image when I update the static-builder.git repo, but I'm wondering what the "proper" method is. Should I expose my registry, build images externally, then push the builder images to it? That feels too manual, and how do I ensure the image is always using the latest upstream `openshift/sti-foo` image each time a user creates a new app from my `static-builder` image? Thanks _______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
