You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Tekton Task responsible to perform the step buildah bud uses a hard coded value to specify the path to execute the command s2i. This parameter should be externalised like also the following s2i images labels using a step0 to correctly let s2i build --as-dockerfile to populate the dockerfile - see discussion
The go containers image tool used by skopeo, buildah, ... provides a parse image function which can be used to collect such info from the s2i image selected
The text was updated successfully, but these errors were encountered:
As we have now a Runtime CRD definition, then I dont think that we still need such step0 task for tekton and we could use the Runtime CRD to include additional METADATA such as:
BaseImage to be used,
K8s Labels to be applied,
List of the commands to be used for oc or kubectl exec
and map the Runtime parameters to the TaskRun
Feature
The Tekton Task responsible to perform the step
buildah bud
uses a hard coded value to specify the path to execute the commands2i
. This parameter should be externalised like also the following s2i images labels using astep0
to correctly lets2i build --as-dockerfile
to populate the dockerfile - see discussionInfo coming from : https://access.redhat.com/containers/?tab=tech-details&get-method=red-hat-login#/registry.access.redhat.com/openjdk/openjdk-8-rhel8
The go containers image tool used by skopeo, buildah, ... provides a parse image function which can be used to collect such info from the s2i image selected
The text was updated successfully, but these errors were encountered: