You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description:
I'm facing frequent permission denied issues on Datadog-Agent and Datadog-Cluster-Agent pods since version 7.57.0. These errors occur when creating and managing APM and DogStatsD sockets, as well as when handling remote config services. Example error:
2024-09-10 08:26:32 UTC | CORE | ERROR | (comp/remote-config/rcservice/rcserviceimpl/rcservice.go:59 in newRemoteConfigServiceOptional) | remote config service not initialized or started: unable to create remote config service: could not remove existing rc db (/opt/datadog-agent/run/remote-config.db): remove /opt/datadog-agent/run/remote-config.db: permission denied
Request:
I kindly request the inclusion of specific user security contexts in test cases before releasing new versions, particularly for Datadog-Agent and Cluster-Agent pods. Here is the Helm chart configuration that I'm using:
Please ensure these specific user contexts (runAsUser: 100 for agent and cluster agent and runAsUser: 10000 for injected libraries when DD_APM_INSTRUMENTATION_VERSION v1) are covered in your tests to prevent permission-related issues in future releases.
The text was updated successfully, but these errors were encountered:
Description:
I'm facing frequent permission denied issues on Datadog-Agent and Datadog-Cluster-Agent pods since version
7.57.0
. These errors occur when creating and managing APM and DogStatsD sockets, as well as when handling remote config services. Example error:Request:
I kindly request the inclusion of specific user security contexts in test cases before releasing new versions, particularly for Datadog-Agent and Cluster-Agent pods. Here is the Helm chart configuration that I'm using:
Please ensure these specific user contexts (
runAsUser: 100
for agent and cluster agent andrunAsUser: 10000
for injected libraries when DD_APM_INSTRUMENTATION_VERSION v1) are covered in your tests to prevent permission-related issues in future releases.The text was updated successfully, but these errors were encountered: