CrashLoopBackOff on using opentelemetry-collector-contrib image from private repository

[anand3493]

Component(s)

cmd/otelcontribcol

What happened?

Description

In our organization we have the policy to use docker images from our own AWS ECR repo.
Hence I had pulled this image "otel/opentelemetry-collector-contrib:0.83.0" and pushed into our AWS ECR and mapped it in the values file.
The pods are getting into CrashLoopBackOff state, while if I simply use "otel/opentelemetry-collector-contrib:0.83.0" this image, the deployment is working fine.

Expected Result

Expecting to deploy using our own docker images

Actual Result

Error:
failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/otelcol-contrib": stat /otelcol-contrib: no such file or directory: unknown

Collector version

0.83.0

Environment information

Environment

Kubernetes

OpenTelemetry Collector configuration

No response

Log output

failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/otelcol-contrib": stat /otelcol-contrib: no such file or directory: unknown

Additional context

No response

[anand3493]

Sorry, my bad. I had supplied operator image incorrectly

[saiganeshkABI]

Can you help us by sharing the correct operator image?

This is the command I used to deploy otel in our aks: