anchor.diff:  
   <pre class='terminal'>$ cf push test-app -o cloudfoundry/test-app</pre>
   
  -###<a id='private'></a>Push a Docker Image using Docker Trusted Registries
  +###<a id='private'></a>Push a Docker Image Using Docker Trusted Registries
   
  -To deploy a Docker image using Docker Trusted Registries, run:
  +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> 
   
  
positive.code: 
  After Garden-runC creates a container, Diego runs and monitors the processes inside of it.
  
  To determine which processes to run, the [Cloud Controller](../concepts/architecture/cloud-controller.html) fetches the metadata associated with the Docker image and returns it to the Cloud Controller. The Cloud Controller uses this metadata to perform the following actions:
  
    * Runs the start command as the user specified in the Docker image
    * Instructs Diego and the [Gorouter](../concepts/architecture/router.html) to route traffic to the lowest-numbered port exposed in the Docker image
  
negative.code: 
  ##<a id='multi-tenant'></a>Docker Security Concerns in a Multi-Tenant Environment##
  
  The attack surface area for a Docker-based container running on Diego remains somewhat higher than that of a buildpack application 
  because Docker allows users to fully specify the contents of their root file systems. A buildpack application runs on a trusted root filesystem.
  
  The Garden-runC provides features that allow the platform to run Docker images more securely in a multi-tenant context. 
  In particular, Cloud Foundry uses the `user-namespacing` feature found on modern Linux kernels to ensure that users cannot gain escalated privileges on the host even if they escalate privileges within a container.
  
  The Cloud Controller always runs Docker containers on Diego with user namespaces enabled. 
  This security restriction prevents certain features, such as the ability to mount FuseFS devices, from working in Docker containers.
  
  To mitigate security concerns, Cloud Foundry recommends that you run only trusted Docker containers on the platform. 
  By default, the Cloud Controller does not allow Docker-based applications to run on the platform.
  
  To allow Docker-based applications to run, a Cloud Controller administrator can enable the `diego_docker` feature flag with the following command:
  <pre class='terminal'>
  