anchor.diff:      }
     }
   }
  -```
  +----
  +====
   
   For pulling the builder Docker image from a private Docker registry, you have to specify
   the `PullSecret` field, which is part of the build strategy definition:
   
  -```
  +====
  +----
   {
     "strategy": {
       "stiStrategy": {
  
positive.code: 
  [#custom-build]
  == Custom Build
  Custom builds are the most sophisticated version of builds, allowing developers to define a builder image which is responsible for the entire process of the build. The custom builder image is a plain Docker image within which the author embeds the logic of the desired build process, such as building RPMs or building
  base Docker images.
  
  [#using-docker-credentials-for-pushing-and-pulling-images]
  == Using Docker Credentials for Pushing and Pulling Images
  
  In case you want to push the output image into a private Docker Registry or pull
  the builder image from the private Docker Registry that requires authentication
  or Docker Hub, you have to supply the `.dockercfg` file with valid Docker
  Registry credentials.
  
  The *_.dockercfg_* JSON file usually exists in your home directory and has
  
negative.code: ----
  ====
  
  Once you have created the `*Secret*`, you can add a `SourceSecret` field into
  the `Source` section inside the `BuildConfig` and set it to the name of the
  `*Secret*` that you created, in this case `*scmsecret*`:
  
  ====
  