Description of problem:

Even though defining environment variablse inside  "Build" resource and seeing these environment variables inside buildah steps, we observe that  "buildah build" process does not use these environments.    We see that while building the Image,     PIP_INDEX_URL environment variable not respected and buildah step tries to connect to default pip urls instead of our internal URLs. So this is different than classic buildconfig build behaviour.  We guess there may be a BUG. 

Prerequisites (if any, like setup, operators/versions):  v1.1

Steps to Reproduce

TaskRun attached

Actual results:

PIP_INDEX_URL env not set

Expected results:

PIP_INDEX_URL env set

Reproducibility (Always/Intermittent/Only Once): Always

Acceptance criteria: 

Definition of Done:

Build Details:

Additional info (Such as Logs, Screenshots, etc):

environment variables specified under "spec.env" of the build resource are not respected while building. We guess that is because "s2i" command is run with "--as-dockerfile" option since we see "Application dockerfile generated in /s2i/Dockerfile" logs from the container. Environment variables are not added to that final dockerfile.

 *