anchor.diff:  stored locally.
   ====
   
  +[[docker-strategy-environment]]
  +=== Environment Variables
  +
  +To make environment variables available to the
  +link:../architecture/core_concepts/builds_and_image_streams.html#docker-build[Docker build]
  +process and resulting image, you can add environment variables to the
  +`*dockerStrategy*` definition of the `*BuildConfig*`.
  +
  +The environment variables defined there are inserted as a single ENV Dockerfile
  +instruction right after the FROM instruction, so that it can be referenced later
  +on within the Dockerfile.
  +
  +The variables are defined during build and stay in the output image, therefore
  +they will be present in any container that runs that image as well.
  +
  +For example, defining a custom HTTP proxy to be used during build and runtime:
  +
  +====
  +
  +----
  +{
  +  "dockerStrategy": {
  +    ...
  +    "env": [
  +      {
  +        "name": "HTTP_PROXY",
  +        "value": "http://myproxy.net:5187/"
  +      }
  +    ]
  +  }
  +}
  +----
  +====
  +
  +
   
   [[custom-strategy-options]]
   
  
positive.code: stored locally.
  ====
  endif::openshift-origin[]
  
  [[using-a-proxy-for-git-cloning]]
  
  
negative.code: ====
  
  [[configuring-the-source-environment]]
  === Environment Variables
  
  There are two ways to make environment variables available to the
  link:../architecture/core_concepts/builds_and_image_streams.html#source-build[source build]
  process and resulting \image: link:#environment-files[environment files] and
  link:#buildconfig-environment[*BuildConfig* environment] values.
  
  