TroubleshootingPDF version

ECS Installation failure due to External Registry issues

During a fresh ECS install, installation failure when pulling images typically indicates incorrect setup of the external or custom registry.

The failure often occurs at the "Install mutating webhook for ECS tolerations" step, where the ecs-toleration-webhook image is the first to be pulled from the custom registry.

Error logs from kubelet may look similar:

Failed to pull image "registry.ecs.internal/cloudera_thirdparty/ecs/ecs-tolerations-webhook:v10": rpc error: code = Unknown desc = failed to pull and unpack image ...

  1. Navigate to Cloudera Manager UI ->Containerized cluster (ECS Cluster Name) ->Configuration.
  2. Search for "docker" and verify the following parameters: External Container Registry User, External Container Registry Password, External Container Registry, External Docker Registry Certificate (PEM format). Only TLS-enabled custom Docker Registry is supported.
  3. If any configurations are incorrect, update and save the changes.
  4. Restart the ECS cluster to apply the changes(All ECS server and agents service need to be restarted. Note that hosts restart is not required.)
  5. Once the command succeeds, navigate to Cloudera Manager UI -> Running Commands, find the failed First Run command, and click Resume to proceed with the installation process.