anchor.diff:  gluster-claim   <none>    Bound     gluster-pv   1Gi        RWX           24s
   ----
   
  -
  -
  -NOTE: If either the *pvc* or *pv* failed to create or the pvc failed to bind, refer back to the
  -link:../persistent_storage/persistent_storage_glusterfs.html[GlusterFS Persistent Storage] guide.
  -*Do not* proceed until they initialize and the pvc status is `Bound`
  +[NOTE]
  +====
  +If either the PVC or PV failed to create or the PVC failed to bind, refer back
  +to the link:../persistent_storage/persistent_storage_glusterfs.html[GlusterFS
  +Persistent Storage] guide. *Do not* proceed until they initialize and the PVC
  +status is *Bound*.
  +====
   
   [[attach-pvc-to-reg]]
   === Attach the PVC to the Docker Registry
   
  -Before moving forward, ensure that the docker-registry service is running.
  +Before moving forward, ensure that the *docker-registry* service is running.
   
   ----
   $ oc get svc
  
positive.code: ----
  ====
  
  When pods are created, they receive a copy of */etc/resolve.conf*, which typically contains
  only the master DNS server so they can resolve external DNS requests.  To enable internal
  DNS resolution, insert the dnsmasq server to the beginning.  This way, dnsmasq will attempt to resolve
  requests internally first.
  
  In */etc/resolve.conf* all scheduled nodes,
  ====
  ----
  nameserver 192.168.1.100  <1>
  nameserver 192.168.1.1    <2>
  ----
  <1> Add the internal DNS server
  <2> Pre-existing External DNS server
  ====
  
  Once the configurations have been changed, restart the OpenShift Master and dnsmasq services.
  
  ifdef::openshift-enterprise[]
  ----
  
negative.code: docker-registry   172.30.167.194   <none>        5000/TCP                docker-registry=default   18m
  ----
  
  [NOTE]
  ====
  If either the *docker-registry* service or its associated pod is not running,
  refer back to the
  link:../install/docker_registry.html#deploy-registry[*docker-registry*] setup
  instructions for troubleshooting before continuing.
  ====
  
  Then, attach the PVC:
  
  ----
  $ oc volume deploymentconfigs/docker-registry --add --name=v1 -t pvc \
       --claim-name=gluster-claim --overwrite
  ----
  
  link:../install/docker_registry.html[Deploying a Docker Registry] provides more
  information on using the Docker registry.
  
  [[backing-docker-registry-with-glusterfs-storage-issues]]
  == Known Issues
  
  [[backing-docker-registry-with-glusterfs-storage-pod-cannot-resolve]]
  === Pod Cannot Resolve the Volume Host
  
  In non-production cases where the *dnsmasq* server is located on the same node
  as the {product-title} master service, pods might not resolve to the host
  machines when mounting the volume, causing errors in the
  *docker-registry-1-deploy* pod. This can happen when *dnsmasq.service* fails to
  start because of a collision with OpenShift DNS on port 53. To run the DNS
  server on the master host, some configurations needs to be changed.
  
  In *_/etc/dnsmasq.conf_*, add:
  
  ====
  ----
  # Reverse DNS record for master
  