anchor.diff:  
   You can override the integrated registry's default configuration, found by
   default at *_/config.yml_* in a running registry's container, with your own
  -custom configuration. See the upstream registry documentation's
  -https://docs.docker.com/registry/configuration/[Registry Configuration
  -Reference] for the full list of available options.
  +custom configuration. See
  +link:#registry-configuration-reference[registry configuration reference] for more
  +information.
  +
  +[TIP]
  +Upstream configuration options in this file may also be overridden using environment
  +variables. However, the link:#middleware[middleware section] may **not** be
  +overridden using environment variables. See upstream documentation on how to
  +link:https://docs.docker.com/registry/configuration/#override-specific-configuration-options[override specific configuration options].
  +
  +=== Deploying Updated Configuration
   
   To enable managing the registry configuration file directly, it
   is recommended that the configuration file be mounted as a
  
positive.code: . link:#deploy-registry[Deploy the registry].
  
  . Edit the registry configuration file locally as needed. The initial YAML file
  deployed on the registry is provided below:
  +
  ====
  ----
  version: 0.1
  
negative.code:   addr: :5000
  storage:
    cache:
      blobdescriptor: inmemory
    filesystem:
      rootdirectory: /registry
    delete:
  