anchor.diff:  # export REGISTRY=$(oc get service docker-registry -t '{{.spec.clusterIP}}{{"\n"}}')
   ----
   
  -. Next, tag all of the builder images before pushing them into the
  -{product-title} Docker registry:
  -+
  -----
  -# docker tag registry.access.redhat.com/jboss-amq-6/amq62-openshift $REGISTRY:5000/openshift/amq62-openshift
  -# docker tag registry.access.redhat.com/jboss-eap-6/eap64-openshift $REGISTRY:5000/openshift/eap64-openshift
  -# docker tag registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift $REGISTRY:5000/openshift/webserver30-tomcat7-openshift
  -# docker tag registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat8-openshift $REGISTRY:5000/openshift/webserver30-tomcat8-openshift
  -# docker tag registry.access.redhat.com/rhscl/mongodb-26-rhel7 $REGISTRY:5000/openshift/mongodb-26-rhel7
  -# docker tag registry.access.redhat.com/rhscl/mysql-56-rhel7 $REGISTRY:5000/openshift/mysql-56-rhel7
  -# docker tag registry.access.redhat.com/rhscl/perl-520-rhel7 $REGISTRY:5000/openshift/perl-520-rhel7
  -# docker tag registry.access.redhat.com/rhscl/php-56-rhel7 $REGISTRY:5000/openshift/php-56-rhel7
  -# docker tag registry.access.redhat.com/rhscl/postgresql-94-rhel7 $REGISTRY:5000/openshift/postgresql-94-rhel7
  -# docker tag registry.access.redhat.com/rhscl/python-27-rhel7 $REGISTRY:5000/openshift/python-27-rhel7
  -# docker tag registry.access.redhat.com/rhscl/python-34-rhel7 $REGISTRY:5000/openshift/python-34-rhel7
  -# docker tag registry.access.redhat.com/rhscl/ruby-22-rhel7 $REGISTRY:5000/openshift/ruby-22-rhel7
  -# docker tag registry.access.redhat.com/openshift3/nodejs-010-rhel7 $REGISTRY:5000/openshift/nodejs-010-rhel7
  +. Next, tag all of the builder images that you synced and exported before
  +pushing them into the {product-title} Docker registry. For example, if you
  +synced and exported only the Tomcat image:
  ++
  +----
  +# docker tag \ 
  +registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift:1.1 \
  +$REGISTRY:5000/openshift/webserver30-tomcat7-openshift:1.1
  +# docker tag \ 
  +registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift:latest \
  +$REGISTRY:5000/openshift/webserver30-tomcat7-openshift:1.2
  +# docker tag \ 
  +registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift:latest \
  +$REGISTRY:5000/openshift/webserver30-tomcat7-openshift:latest
   ----
   
   [[disconnected-creating-an-admin-user]]
  
positive.code: repository is accessible from the {product-title} nodes. Installing the source
  control repository is outside the scope of this document.
  
  Also, when you try building applications in {product-title}, your build may have
  some external dependencies, such as a Maven Repository or Gem files for Ruby
  applications. By default, Red Hat Docker images try to reach out to external
  repositories on the Internet. 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]
  ====
  
negative.code:     registry.access.redhat.com/openshift3/metrics-heapster
  ----
  
  . Export the S2I builder images that you synced in the previous section. For
  example, if you synced only the Tomcat image:
  +
  ----
  # docker save -o ose3-builder-images.tar \
      registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift:latest \
      registry.access.redhat.com/jboss-webserver-3/webserver30-tomcat7-openshift:1.1 \
  ----
  
  [[disconnected-repo-server]]
  