We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agent Environment Initially found on 7.55.2, also tested on 7.55.3, latest, and 7-beta (the most recent push to dockerhub)
Describe what happened: When otelCollector.enabled is set to true in the Helm chart, a container is added to the pod called otel-agent, with a command of
otelCollector.enabled
true
otel-agent
command: ["otel-agent", "-foreground", "-config={{ template "datadog.otelconfPath" . }}/datadog.yaml"]
When the container tries to start, the following occurs:
message: 'failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "otel-agent": executable file not found in $PATH: unknown'
Describe what you expected: The otel-agent binary to be present and the container to start
Steps to reproduce the issue: Install the Datadog Helm chart with the below
datadog: apiKey: <yoink> clusterName: demo otelCollector: enabled: true
and the pod will not start.
This can also be tested in the images on dockerhub
$ docker run -it datadog/agent:7-beta bash root@a5bfaa78b3f9:/# find / -name 'otel*' /opt/entrypoints/otel-agent root@a5bfaa78b3f9:/# cat /opt/entrypoints/otel-agent #!/usr/bin/env bash set -euo pipefail exec /opt/datadog-agent/embedded/bin/otel-agent --config /etc/datadog-agent/otel-config.yaml root@a5bfaa78b3f9:/# /opt/datadog-agent/embedded/bin/otel-agent bash: /opt/datadog-agent/embedded/bin/otel-agent: No such file or directory
The text was updated successfully, but these errors were encountered:
Same problem here =/
Sorry, something went wrong.
No branches or pull requests
Agent Environment
Initially found on 7.55.2, also tested on 7.55.3, latest, and 7-beta (the most recent push to dockerhub)
Describe what happened:
When
otelCollector.enabled
is set totrue
in the Helm chart, a container is added to the pod calledotel-agent
, with a command ofWhen the container tries to start, the following occurs:
Describe what you expected:
The otel-agent binary to be present and the container to start
Steps to reproduce the issue:
Install the Datadog Helm chart with the below
and the pod will not start.
This can also be tested in the images on dockerhub
The text was updated successfully, but these errors were encountered: