anchor.diff:  
   To deploy the integrated OpenShift
   link:../architecture/infrastructure_components/image_registry.html[Docker
  -Registry], run the `oadm registry` command as a user with cluster
  -administrator privileges:
  -
  -----
  -$ oadm registry --config=admin.kubeconfig --credentials=openshift-registry.kubeconfig
  -----
  -
  -where the value passed to `--config` is the path to the kubeconfig file for the
  -cluster administrator, and `--credentials` is the path to the kubeconfig file
  -for the openshift-registry.
  -
  -This creates a service called `docker-registry` and a deployment config called
  -`docker-registry`. Once deployed successfully, there will be a pod with a name
  -similar to `docker-registry-1-cpty9`.
  -
  -For a full list of options you can specify when creating the registry, please
  -see `oadm registry --help`.
  +registry], run the following command as a user with cluster administrator
  +privileges:
  +
  +====
  +----
  +$ oadm registry --config=admin.kubeconfig \
  +    --credentials=openshift-registry.kubeconfig
  +----
  +<1> `--config` is the path to the *_kubeconfig_* file for the cluster
  +administrator.
  +<2> `--credentials` is the path to the *_kubeconfig_* file for the
  +*openshift-registry*.
  +====
  +
  +This creates a service and a deployment configuration, both called
  +*docker-registry*. Once deployed successfully, a pod is created with a name
  +similar to *docker-registry-1-cpty9*.
  +
  +To see a full list of options that you can specify when creating the registry:
  +
  +----
  +$ oadm registry --help
  +----
   
   == Viewing Logs
   
  -To view the logs for the Docker Registry, simply run the `oc log` command for
  -the pod(s) for the Registry. For example:
  -
  -[options="nowrap"]
  -----
  -$ oc log docker-registry-1-da73t
  +To view the logs for the Docker registry, run the `oc logs` command for the
  +pod(s) for the registry. For example:
  +
  +====
  +[options="nowrap"]
  +----
  +$ oc logs docker-registry-1-da73t
   2015-05-01T19:48:36.300593110Z time="2015-05-01T19:48:36Z" level=info msg="version=v2.0.0+unknown"
   2015-05-01T19:48:36.303294724Z time="2015-05-01T19:48:36Z" level=info msg="redis not configured" instance.id=9ed6c43d-23ee-453f-9a4b-031fea646002
   2015-05-01T19:48:36.303422845Z time="2015-05-01T19:48:36Z" level=info msg="using inmemory layerinfo cache" instance.id=9ed6c43d-23ee-453f-9a4b-031fea646002
   2015-05-01T19:48:36.303433991Z time="2015-05-01T19:48:36Z" level=info msg="Using OpenShift Auth handler"
   2015-05-01T19:48:36.303439084Z time="2015-05-01T19:48:36Z" level=info msg="listening on :5000" instance.id=9ed6c43d-23ee-453f-9a4b-031fea646002
   ----
  +====
   
   == File Storage
   
  -Tag and image metadata is stored in OpenShift, but the Registry owns layer and signature data. The Registry stores data in a volume that is mounted into the registry container at `/registry`. You can `oc exec` into the Registry container to see the contents:
  +Tag and image metadata is stored in OpenShift, but the registry owns layer and
  +signature data. The registry stores data in a volume that is mounted into the
  +registry container at *_/registry_*. You can
  +link:../dev_guide/executing_remote_commands.html[execute a remote command] in
  +the registry container to see the contents:
   
   [options="nowrap"]
   ----
  
positive.code: $ oc log docker-registry-1-da73t | grep tls
  time="2015-05-27T05:05:53Z" level=info msg="listening on :5000, tls" instance.id=deeba528-c478-41f5-b751-dc48e4935fc2
  ----
  +
  . Copy CA certificate to the docker certs dir. This must be done on all nodes in the cluster.
  +
  ----
  $ sudo mkdir -p /etc/docker/certs.d/172.30.124.220:5000
  $ sudo cp ca.crt /etc/docker/certs.d/172.30.124.220:5000
  
negative.code: cf2616975b4a: Image successfully pushed
  Digest: sha256:3662dd821983bc4326bee12caec61367e7fb6f6a3ee547cbaff98f77403cab55
  ----
  ====
  