anchor.diff:  ifdef::openshift-origin[]
   To deploy the integrated Docker registry, use the `oadm registry` command from
   the *_admin.kubeconfig_* file's location, as a user with cluster administrator
  -privileges. For example:
  +privileges:
   
   ----
   $ oadm registry --config=admin.kubeconfig \//<1>
  
positive.code: ----
  ====
  +
  . link:#access[Log in to the registry] using the information from securing the registry.  However,
  this time point to the host name used in the route rather than your service IP.  You should
  now be able to tag and push images using the route host:
  +
  ====
  ----
  
negative.code: 
  [IMPORTANT]
  ====
  The `--mount-host` option mounts a directory from the node on which the registry
  container lives. If you scale up the *docker-registry* deployment configuration,
  it is possible that your registry pods and containers will run on different
  nodes, which can result in two or more registry containers, each with its own
  local storage. This will lead to unpredictable behavior, as subsequent requests
  to pull the same image repeatedly may not always succeed, depending on which
  container the request ultimately goes to.
  ====
  
  The `--mount-host` option requires that the registry container run in privileged
  mode. This is automatically enabled when you specify `--mount-host`.
  However, not all pods are allowed to run
  link:prerequisites.html#security-warning[privileged containers] by default. If
  you still want to use this option:
  
  . Create a new link:../../admin_guide/service_accounts.html[service account] in
  the *default* project for the registry to run as. The following example creates
  a service account named *registry*:
  +
  ----
  $ echo \
  