Skip to content

[upstream] JVM Agent fails to initialize on k8s with containerd runtime #2328

@clawoflight

Description

@clawoflight

Hi, the current version 3.2.11 is affected by open-telemetry/opentelemetry-java#4507, which completely prevents the agent from starting when containerd is used as runtime.
The bug was fixed in OpenTelemetry 1.15.

Would it be possible to upgrade to that with the 3.3 agent? Not receiving any telemetry is very annoying :)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions