APM LINUX OS Agent Restriction on monitoring docker containers as non-root user
NormanKrueger 110000QH3M Visits (511)
The blog wants to help you monitor docker instances with an agent that was installed as a non root user.
Reference: csdnkrue 2019
IJ15216: LINUX OS AGENT DOCUMENTATION DOES NOT INCLUDE RESTRICTION ON MONITORING DOCKER AS NON-ROOT
Manage Docker as a non-root user
Problem Description: The Linux OS agent fails to monitor docker information when the LZ agent is run as non-root user and there is no documentation of this limitation. Workaround: In order for the APM OS agent to be able to gather "Docker" attribute data, the user running the klzagent process must have file/directory access permission to Docker directories, AND the user must be able to run commands that gather data from the Docker daemon. By default, Docker daemon binds to a socket owned by "root", requiring "root" authority when running commands to the Docker daemon by prefacing commands with "sudo" for non-root users, or configuring the environment where the user is a member of the "docker" group. Manage Docker as a non-root user: http
Subscribe and follow us for all the latest information directly on your social feeds: