anchor.diff:       --to=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY} \
        --to-release-image=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:${OCP_RELEASE}-${ARCHITECTURE}
   ----
  +endif::[]
   +
   This command pulls the release information as a digest, and its output includes
   the `imageContentSources` data that you require when you install your cluster.
  
positive.code: 
  .. Export the release mirror:
  +
  [source,terminal]
  ----
  $ RELEASE_NAME="ocp-release"
  ----
  +
  For a production release, you must specify `ocp-release`.
  
  .. Export the type of architecture for your server, such as `x86_64`.:
  +
  [source,terminal]
  ----
  $ ARCHITECTURE=<server_architecture>
  ----
  
  .. Export the path to the directory to host the mirrored images:
  +
  
negative.code:      --to=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY} \
       --to-release-image=${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:${OCP_RELEASE}-${ARCHITECTURE} --dry-run
  ----
  endif::[]
  
  ... Record the entire `imageContentSources` section from the output of the previous
  command. The information about your mirrors is unique to your mirrored repository, and you must add the `imageContentSources` section to the `install-config.yaml` file during installation.
  ... Mirror the images to a directory on the removable media:
  +
  ifdef::openshift-origin[]
  [source,terminal]
  ----
  $ oc adm release mirror -a ${LOCAL_SECRET_JSON} --to-dir=${REMOVABLE_MEDIA_PATH}/mirror quay.io/${PRODUCT_REPO}/${RELEASE_NAME}:${OCP_RELEASE}
  ----
  endif::[]
  ifndef::openshift-origin[]
  [source,terminal]
  ----
  $ oc adm release mirror -a ${LOCAL_SECRET_JSON} --to-dir=${REMOVABLE_MEDIA_PATH}/mirror quay.io/${PRODUCT_REPO}/${RELEASE_NAME}:${OCP_RELEASE}-${ARCHITECTURE}
  ----
  endif::[]
  
  ... Take the media to the restricted network environment and upload the images to the local container registry.
  +
  [source,terminal]
  