Back-off restarting failed container opentelemetry-auto-instrumentation in pod

[dartagnanli]

Describe the bug

when i inject the auto-instrumentation container for my pod ,and then my pod is not ready ,

Normal   Scheduled  13m                   default-scheduler  Successfully assigned luban/openapi-86c5f46479-26lhw to gms-3
  Normal   Pulled     13m                   kubelet            Container image "xxxxxx/openapi:v1.4.4" already present on machine
  Normal   Created    13m                   kubelet            Created container openapi
  Normal   Started    13m                   kubelet            Started container openapi
  Normal   Pulled     12m (x5 over 13m)     kubelet            Container image "xxxxxx/autoinstrumentation-go:v0.16.0-alpha" already present on machine
  Normal   Created    12m (x5 over 13m)     kubelet            Created container opentelemetry-auto-instrumentation
  Normal   Started    12m (x5 over 13m)     kubelet            Started container opentelemetry-auto-instrumentation
  Warning  BackOff    3m44s (x46 over 13m)  kubelet            Back-off restarting failed container opentelemetry-auto-instrumentation in pod openapi-86c5f46479-26lhw_luban(be4c2d6b-723c-4263-a6b0-2fc09812e9d5)

but when i run it in host machine,like blew ,it is ok and will not be exited

sudo OTEL_GO_AUTO_TARGET_EXE=/home/xxx//openapi SERVICE_NAME=my_service OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318 ./otel-go-instrumentation

my otel-go-instrumentation version is v0.15.0-alpha

Environment

• OS: Linux debian12-1-11 6.1.0-18-amd64 Kick-off Go auto-instrumentation group #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64 GNU/Linux
• Go Version: 1.23.2
• Version: v0.15.0-alpha

[damemi]

Hi, could you please share the logs from the auto-instrumentation container?

[dartagnanli]

this is no error log ,all is blew

{"time":"2024-11-01T08:42:52.238546198Z","level":"INFO","source":{"function":"main.main","file":"/app/cli/main.go","line":103},"msg":"building OpenTelemetry Go instrumentation ...","globalImpl":false,"version":{"Release":"v0.16.0-alpha","Revision":"unknown","Go":{"Version":"go1.23.2","OS":"linux","Arch":"amd64"}}}
{"time":"2024-11-01T08:42:54.239305134Z","level":"INFO","source":{"function":"go.opentelemetry.io/auto/internal/pkg/process.(*Analyzer).DiscoverProcessID","file":"/app/internal/pkg/process/discover.go","line":64},"msg":"found process","pid":7}

[MrAlias]

The lack of error message or a stacktrace from a panic/crash makes it seem like the pod is killing itself. Is there a healthcheck for the pod that is isn't being satisfied?

[RonFed]

Might be related to #902

[dartagnanli]

Might be related to #902

Similar！Is there any solution about this？

[dartagnanli]

I raise my Instrumentation config go.resourceRequirements, it seem went well.Thanks