anchor.diff:  
   To deploy a Docker image using Docker trusted registries, run:
   
  - <pre class='terminal'>$ cf push my-app -o MY-PRIVATE-REGISTRY.DOMAIN:5000/image/name:v2</pre>
  +<pre class='terminal'>$ cf push my-app -o MY-PRIVATE-REGISTRY.DOMAIN:5000/image/name:v2
  +</pre>
   
  - Replace `MY-PRIVATE-REGISTRY.DOMAIN` with your domain name, which resolves to the private registry.
  -In this example, 5000 is the port on which your private registry serves traffic. `image/name` is the name of the Docker image repository. `v2` is a tag in that repository that refers to a specific image.
  +Replace `MY-PRIVATE-REGISTRY.DOMAIN` with your domain name, which resolves to 
  +the private registry.
  +In this example, 5000 is the port on which your private registry serves traffic. 
  +`image/name` is the name of the Docker image repository. 
  +`v2` is a tag in that repository that refers to a specific image.
   
   ###<a id='volume'></a> Docker Volume Support
   
  -Diego now supports Docker volumes. More information can be found [here](https://docs.cloudfoundry.org/devguide/services/using-vol-services.html) on how to enable volume support, and the limitations of NFS volumes within the [NFS Bosh Volume Release](https://github.com/cloudfoundry-incubator/nfs-volume-release#special-notes-for-docker-image-based-apps).
  +Diego now supports Docker volumes. 
  +More information can be found 
  +[here](https://docs.cloudfoundry.org/devguide/services/using-vol-services.html) 
  +on how to enable volume support, and the limitations of NFS volumes within the 
  +[NFS Bosh Volume Release](https://github.com/cloudfoundry-incubator/nfs-volume-release#special-notes-for-docker-image-based-apps).
  
positive.code: 
  ##<a id='push-docker'></a>Push a Docker Image with the cf CLI
  
  Follow these instructions to deploy updated or new Docker images using the Cloud Foundry Command Line Interface (cf CLI).
  
  To perform the procedures in this topic, you must install cf CLI v6.13.0 or later. See <a href="../cf-cli/install-go-cli.html">Installing the cf CLI</a> for more information.
  For information about pushing a Docker image with a previous version of the cf CLI, see <a href= 'https://github.com/cloudfoundry-incubator/diego-design-notes/blob/master/docker-support.md'>Docker Support in CF + Diego</a>.
  
  When pushing an app, you specify either a Docker image on Docker Hub or a URI to a trusted Docker registry. Diego does not support using private registries.
  Also, when using Diego, you must use a registry that supports the <a href="https://docs.docker.com/registry/spec/api/">Docker Registry API V2</a>.
  
  ###<a id='public'></a>Push a Docker Image Using Docker Hub
  
  Run `cf push test-app -o cloudfoundry/MY-DOCKER-IMAGE` to deploy a Docker image. Replace `MY-DOCKER-IMAGE` with the name of an image from an accessible Docker Registry.
  
  For example, the following command pushes the `test-app` on Docker Hub to Cloud Foundry:
  
  <pre class='terminal'>$ cf push test-app -o cloudfoundry/test-app</pre>
  
  
negative.code: This topic provides information about how Docker works in Cloud Foundry and describes how to push an application with a Docker image.
  For information about Diego, see the [Diego Architecture](../concepts/diego/diego-architecture.html) topic.
  
  In addition to the default Linux environment provided by Cloud Foundry, 
  operators can specify a Docker image that provides the file system used by the 
  container.
  When pushing an app, you can specify the location of the docker image you want 
  to use.
  
  A Docker image consists of a collection of layers.
  Each layer consists of one or both of the following:
  