opentelemetry-auto-instrumentation-dotnet init container just fails to start

[ymor]

Image: 602401143452.dkr.ecr.eu-west-2.amazonaws.com/eks/observability/adot-autoinstrumentation-dotnet:v1.2.0

cp: preserving times for '/otel-auto-instrumentation-dotnet/.': Operation not permitted

This is the only log from the container itself.

Describe logs:

opentelemetry-auto-instrumentation-dotnet:
    Container ID:  containerd://59e667e0ec408c37a61850defce4ca0ec60a8570b09cc10a8d75a577fd848eb0
    Image:         602401143452.dkr.ecr.eu-west-2.amazonaws.com/eks/observability/adot-autoinstrumentation-dotnet:v1.2.0
    Image ID:      602401143452.dkr.ecr.eu-west-2.amazonaws.com/eks/observability/adot-autoinstrumentation-dotnet@sha256:e22607f4032502c4f971e249de5686ec7ed30c75f9cc180a405173b3992aa4fd
    Port:          <none>
    Host Port:     <none>
    Command:
      cp
      -a
      /autoinstrumentation/.
      /otel-auto-instrumentation-dotnet
    State:          Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 04 Sep 2024 11:04:10 +0000
      Finished:     Wed, 04 Sep 2024 11:04:10 +0000
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Wed, 04 Sep 2024 11:03:17 +0000
      Finished:     Wed, 04 Sep 2024 11:03:17 +0000
    Ready:          False
    Restart Count:  4
    Limits:
      cpu:     500m
      memory:  128Mi
    Requests:
      cpu:     50m
      memory:  128Mi

Same issue occurs when I annotate any of my .net (8) applications using instrumentation.opentelemetry.io/inject-dotnet: "true"

[pxaws]

The error indicates that the cp command is attempting to preserve the original file timestamps (such as access time and modification time) during the copy operation, but it doesn't have the necessary permissions to do so. I guess sometime the file system might not support support preserving timestamps or has restricted permissions.

I think we need more information to reproduce the issue on our end. Could you provide information regarding the EKS cluster and the filesystem that you use for your application (or how you configure it)?

[ymor]

Hi, Sorry I forgot about this. I'll don't think that message is actually anything to do with why it isn't working. But nothing else was been logged. I have updated the Aws observability add on our EKS cluster this week. I shall give this another go and get back to you. Feel free to close this for now. Thanks. Sent from Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Ping Xiang ***@***.***> Sent: Thursday, October 17, 2024 7:45:42 PM To: aws-observability/aws-otel-dotnet-instrumentation ***@***.***> Cc: Mark Hebden ***@***.***>; Author ***@***.***> Subject: Re: [aws-observability/aws-otel-dotnet-instrumentation] opentelemetry-auto-instrumentation-dotnet init container just fails to start (Issue #100) The error indicates that the cp command is attempting to preserve the original file timestamps (such as access time and modification time) during the copy operation, but it doesn't have the necessary permissions to do so. I guess sometime the file system might not support support preserving timestamps or has restricted permissions. I think we need more information to reproduce the issue on our end. Could you provide information regarding the EKS cluster and the filesystem that you use for your application (or how you configure it)? — Reply to this email directly, view it on GitHub<#100 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAUTUFFTLMYXV5R4WJT7MELZ4AAVNAVCNFSM6AAAAABNUCJPC2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRQGI4DKMBWGQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>