anchor.diff:  # docker pull registry.access.redhat.com/openshift3/metrics-heapster
   ----
   
  -. Pull Red Hat’s certified
  +. Pull the Red Hat-certified
   xref:../../architecture/core_concepts/builds_and_image_streams.adoc#source-build[Source-to-Image
  -(S2I)] builder images. S2I is the process that {product-title} uses to take
  -application code and build it into a Docker image to run on the platform.
  -+
  -Any languages, runtimes, or databases that you do not intend to use can be
  -skipped:
  -+
  -----
  -# docker pull registry.access.redhat.com/jboss-amq-6/amq62-openshift
  -# docker pull registry.access.redhat.com/jboss-eap-6/eap64-openshift
  -# docker pull registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift
  -# docker pull registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat8-openshift
  -# docker pull registry.access.redhat.com/rhscl/mongodb-26-rhel7
  -# docker pull registry.access.redhat.com/rhscl/mysql-56-rhel7
  -# docker pull registry.access.redhat.com/rhscl/perl-520-rhel7
  -# docker pull registry.access.redhat.com/rhscl/php-56-rhel7
  -# docker pull registry.access.redhat.com/rhscl/postgresql-94-rhel7
  -# docker pull registry.access.redhat.com/rhscl/python-27-rhel7
  -# docker pull registry.access.redhat.com/rhscl/python-34-rhel7
  -# docker pull registry.access.redhat.com/rhscl/ruby-22-rhel7
  -# docker pull registry.access.redhat.com/openshift3/nodejs-010-rhel7
  +(S2I)] builder images that you intend to use in your OpenShift environment. You
  +can pull the following images:
  ++
  +* jboss-eap70-openshift
  +* jboss-amq-62
  +* jboss-datagrid65-openshift
  +* jboss-decisionserver62-openshift
  +* jboss-eap64-openshift
  +* jboss-eap70-openshift 
  +* jboss-webserver30-tomcat7-openshift 
  +* jboss-webserver30-tomcat8-openshift  
  +* mongodb
  +* mysql
  +* nodejs
  +* perl 
  +* php 
  +* postgresql 
  +* python 
  +* redhat-sso70-openshift
  +* ruby
  ++
  +Make sure to indicate the correct tag specifying the desired version number. For
  +example, to pull both the previous and latest version of the Tomcat image:
  ++
  +----
  +# docker pull \ 
  +registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift:latest
  +# docker pull \ 
  +registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift:1.1
   ----
   
   [[disconnected-preparing-images-for-export]]
  
positive.code:     registry.access.redhat.com/openshift3/metrics-heapster
  ----
  
  . Export the S2I builder images, making sure to remove any items that you did
  not sync in the previous section:
  +
  ----
  # docker save -o ose3-builder-images.tar \
      registry.access.redhat.com/jboss-amq-6/amq62-openshift \
      registry.access.redhat.com/jboss-eap-6/eap64-openshift \
      registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift \
      registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat8-openshift \
      registry.access.redhat.com/rhscl/mongodb-26-rhel7 \
      registry.access.redhat.com/rhscl/mysql-56-rhel7 \
      registry.access.redhat.com/rhscl/perl-520-rhel7 \
      registry.access.redhat.com/rhscl/php-56-rhel7 \
      registry.access.redhat.com/rhscl/postgresql-94-rhel7 \
      registry.access.redhat.com/rhscl/python-27-rhel7 \
      registry.access.redhat.com/rhscl/python-34-rhel7 \
      registry.access.redhat.com/rhscl/ruby-22-rhel7 \
      registry.access.redhat.com/openshift3/nodejs-010-rhel7
  ----
  
  [[disconnected-repo-server]]
  
negative.code: repository is accessible from the {product-title} nodes. Installing the source
  control repository is outside the scope of this document.
  
  Also, when building applications in {product-title}, your build may have some
  external dependencies, such as a Maven Repository or Gem files for Ruby
  applications. For this reason, and because they might require certain tags, many
  of the Quickstart templates offered by {product-title} may not work on a
  disconnected environment. However, while Red Hat Docker images try to reach out
  to external repositories by default, you can configure {product-title} to use
  your own internal repositories. For the purposes of this document, we assume
  that such internal repositories already exist and are accessible from the
  {product-title} nodes hosts. Installing such repositories is outside the scope
  of this document.
  
  [NOTE]
  ====
  