Any agent registration in k8s cluster with crictl runtime failed

Note: This category is not monitored by Support but Relics do contribute.

Tell us what’s happening. any attempt to register newrelic agent fails due to docker socket not found. Which is expected due to setup is based on crio runtime and dockerd new socket value

  • Describe the problem, include screenshots and error messages where applicable
  • Provide the steps to replicate the issue
  • Which versions of affected components are you using?
  • Provide Code/Query snippet (with hints about how to format)

Share some additional context.

  • Steps taken to resolve the issue. What docs etc. have you looked at? What did you try?
  • What should we know about what you see with New Relic that may be impacting the problem?
  • What should we know about your run time environment that may be impacting the problem?

Hi @kostya

Thanks for reaching out for support, I hope you are well.

In order to gain a correct insight of the issue can you confirm the below details using the agents category template;

Agents question template

Please describe the behaviour you are seeing, and how that differs from what you expect.

Please provide information on your environment, and any further information you believe is relevant, such as the below:

  • APM Agent Language
  • APM Agent Version
  • Operating System
  • Operating System Version
  • Frameworks your app is using
  • A link to the application in the New Relic UI.

Additional Resources

Please run New Relic Diagnostics on your applications and share relevant results here. Please do not include the entire file as it contains your license key.