Pod metrics are not collected in containerd runtime.

[vasireddy99]

Describe the bug
When using Bottlerocket in EKS, otel-collector can not collect Pod metrics.
Log is bellow.

2022-03-20T14:04:42.986Z warn cadvisor/container_info_processor.go:93 No pod metric collected {"kind": "receiver", "name": "awscontainerinsightreceiver", "metrics count": 27}
Steps to reproduce

Create cluster with Bottlerocket
Set aws-otel-collector with aws-otel-collector/deployment-template/eks/otel-container-insights-infra.yaml
I use amazon/aws-otel-collector:v0.17.0 image.

This would required changes in awscontainerinsightsreceiver. Reference issue in distro

• Do not collect pod metrics using Bottlerocket aws-observability/aws-otel-collector#1071

Steps to reproduce
If possible, provide a recipe for reproducing the error.

What version did you use?
Version: v0.54.0

What config did you use?

• https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/awscontainerinsightreceiver#sample-configuration-for-container-insights
• https://github.com/aws-observability/aws-otel-collector/blob/main/deployment-template/eks/otel-container-insights-infra.yaml

Additional context
Add any other context about the problem here.

[github-actions]

Pinging code owners: @Aneurysm9 @pxaws

[vasireddy99]

The fix to this issue has been fixed in this PR and is in out on #v0.57.2.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• receiver/awscontainerinsight: @Aneurysm9 @pxaws

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.