After working with appDynamics support, the missing piece for us was to run the machine agent container using the DAEMON strategy in ECS:
Once we did this, we got past the errors and were able to start the container.
Additionally, we had to add the following mounts to the task definition
... View more
I am also looking for this information.
I'm already deploying the java application agent in each of my docker containers running in ECS.
However what I am trying to do specifically is run the machine agent as a docker container as discussed in these resources:
When we ultimately start to run the container via the ECS task, we get the following error:
Could not start up the machine agent due to: Failed to get a response from /info using a GET request. The error encountered is: javax.xml.ws.WebServiceException: Cannot connect to Docker. The unix socket file /var/run/docker.sock does not exist. Please provide a valid file to access.
Details: Container = server agent image (with integrated docker visibility): docker pull store/appdynamics/machine:4.4
The following environment variables are getting set: APPDYNAMICS_AGENT_APPLICATION_NAME = xxx APPDYNANNICS_SIM_ENABLED = true APPDYNAMICS_DOCKER_ENABLED = true APPDYNAMICS_AGENT_NODE_NAME = xxx APPDYNAMICS_AGENT_TIER_NAME = xxx
APPDYNAMICS_CONTROLLER_HOST_NAME = xxx
APPDYNAMICS_AGENT_ACCOUNT_NAME = xxx
APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY = xxx
APPDYNAMICS_CONTROLLER_SSL_ENABLED = xxx
APPDYNAMICS_CONTROLLER_PORT = xxx
The DAEMON strategy is being used in ECS for the task.
Note – I did not configure any ports for the appdynamics agent. It did not appear per documentation this was required – nor could I tell what port needed to be mapped in the ECS task, so none was specified.
... View more