anchor.diff:  $ podman login <target_registry>
   ----
   
  -. Run the source index image that you want to prune in a container. For example:
  +. Determine the list of packages you want to include in your pruned index.
  +
  +.. Run the source index image that you want to prune in a container. For example:
   +
   [source,terminal,subs="attributes+"]
   ----
  
positive.code: ifeval::["{context}" != "olm-managing-custom-catalogs"]
  When configuring Operator Lifecycle Manager (OLM) to use mirrored content on restricted network {product-title} clusters, use this pruning method if you want to only mirror a subset of Operators from the default catalogs.
  
  For the steps in this procedure, the target registry is an existing mirror registry that is accessible by both your cluster and a workstation with unrestricted network access. This example also shows mirroring the default `{catalog-name}` catalog, but the process is the same for all catalogs.
  endif::[]
  
  .Prerequisites
  
negative.code: INFO[0000] serving registry                              database=/database/index.db port=50051
  ----
  
  .. In a separate terminal session, use the `grpcurl` command to get a list of the packages provided by the index:
  +
  [source,terminal]
  ----
  $ grpcurl -plaintext localhost:50051 api.Registry/ListPackages > packages.out
  ----
  
  .. Inspect the `packages.out` file and identify which package names from this list you want to keep in your pruned index. For example:
  +
  .Example snippets of packages list
  [source,text,subs="attributes+"]
  