Splunk AppDynamics

Docker - machine agent issue

Harsh_Shinde
New Member

I cloned the image from https://github.com/Appdynamics/docker-machine-agent

and executed the docker-compose up command after the machine agent installation.

But im getting below error while starting the machine agent, can anyone help please??

"$ docker-compose up
Creating docker-machine-agent ... done
Attaching to docker-machine-agent
docker-machine-agent | /bin/sh: 1: /opt/appdynamics/machine-agent//start-appdynamics: not found
docker-machine-agent exited with code 127"

I dont know what is wrong with this

Labels (1)
Tags (2)
0 Karma

Hiroki_Ito
Contributor
Hello Harsh,

Thanks for posting to the AppDynamics Community.

I cloned the same image with the latest machine agent, v21.5.0, and machine agent could start successfully.

However, from the log, there is an unnecessary slash before "start-appdynamics", so could you remove the last slash from MACHINE_AGENT_HOME variable in Dockerfile and try to run again?
"/opt/appdynamics/machine-agent//start-appdynamics"
->slash after machine-agent is unnecessary

If modifying Dockerfile and using the latest machine agent doesn't work, could you please share whole docker log?

Best Regards,

Hiroki
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...