= Operator-backed {product-very-short} instances might fail to start when using a mirrored plugin catalog index image Using the `mirror-plugins.sh` script to mirror the plugin catalog index image in a disconnected environment might cause Operator-backed {product} ({product-very-short}) instances to fail to start. Running the script rebuilds the catalog index image after replacing all plugin OCI references. If you subsequently use that mirrored catalog index image in your Backstage custom resource (CR), the init container fails to start and logs an error similar to the following: [source,text] ---- InstallException: Cannot use {{inherit}} for oci://registry.access.redhat.com/rhdh/red-hat-developer-hub-backstage-plugin-orchestrator: no existing plugin configuration found. Ensure a plugin from this image is defined in an included file with an explicit version. ---- This occurs because the `install-dynamic-plugins` process resolves OCI references and attempts to merge plugin configurations even for plugins that are disabled by default in the Operator's configuration. This issue specifically affects Operator-backed instances of RHDH. As a workaround, manually empty the default `plugins` list in the Operator's default `ConfigMap`. + [NOTE] ==== These manual changes are reverted when the Operator is upgraded. ==== . Edit the `rhdh-default-config` ConfigMap located in the `rhdh-operator` namespace. . Locate the `dynamic-plugins.yaml` key within the ConfigMap data. . Modify the `plugins` field so that it is an empty list (`plugins: []`), as shown in the example below: + [source,yaml] ---- # -- Truncated --   dynamic-plugins.yaml: |     apiVersion: v1     kind: ConfigMap     metadata:       name: default-dynamic-plugins     data:       dynamic-plugins.yaml: |         includes:           - dynamic-plugins.default.yaml         plugins: [] # -- Truncated -- ---- . Save the ConfigMap and wait a few seconds for the changes to automatically propagate to the Operator pod.