STI via Openshift Console does not work with own Builderimage in OSE3 Dockerregistry
Issue
-
I've made my own STI builderimage for the IBM Liberty Application Server which is pushed into the OSE3 Docker Registry and provided as Imagestream so it is displayed as a builder image on the openshift STI console.
-
Unfortunately it is not possible to perform a STI Build via the Openshift Console:
master1 openshift-master: E0720 15:14:02.054351 88119 factory.go:35] Build failed with error demo/xyz-1: failed to create pod for Build demo/xyz-1: Pod "xyz-1-build" is invalid: spec.volumes[2].name: duplicate value 'builder-dockercfg-d813v'
-
This prevents that the builder could pull the image out of the ose3 docker registry in order to do the STI build
-
This seems related to this
https://bugzilla.redhat.com/show_bug.cgi?id=1232694 -
Indeed manually changing the build config so that there are different names for push and pull secret - but the secret itself is the same solves the problem manually. Is there a fix planned for the OSE3 GA.
Environment
- Openshift 3.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.