Closed ppennanen closed 1 month ago
To silence the error add the environment value DD_CRI_SOCKET_PATH
set to null
:
apiVersion: datadoghq.com/v1alpha1
kind: DatadogAgent
metadata:
name: datadog-agent
namespace: datadog
spec:
credentials:
apiKeyExistingSecret: dd-api-key
agent:
config:
env:
- name: DD_CRI_SOCKET_PATH
value: null
tolerations:
- operator: Exists
apm:
enabled: true
log:
enabled: true
image:
name: "datadog/agent:7.18.1"
process:
enabled: true
systemProbe:
enabled: true
Hi @ppennanen
Thank you for reporting this and for the workaround that you suggested (by setting DD_CRI_SOCKET_PATH
to null
)
We're aware of this issue and we're working on a fix
We also saw the kubelet
check warning in the logs you've shared and we fixed it.
The two fixes will be included in the next datadog-operator
release.
Thanks!
Bulk resolving DatadogAgent v1alpha1
issues.
Describe what happened:
datadog-agent
created bydatadog-operator
running ondocker
logs errors like this:This looks like the same issue as criutil failure that was resolved by Do not enable the
cri
check when running on adocker
setup.The agent has the environment variable
Describe what you expected:
That the agent would not try to use the docker socket as a CRI socket.
Steps to reproduce the issue:
Additional environment details (Operating System, Cloud provider, etc):
GKE. Ubuntu with Docker.