Skip to content

Absolute paths in the example agent.cfg don't match with internal paths for image mtconnect/agent:2.2.0.16 #251

Open
@Dowster64

Description

@Dowster64

Hi,
We installed Ladder using git clone onto a chromebook on 7/5/24 (UK/ AUS format date) . We had to modify the Grafana port from port 80 (I think to >1000) - we used 3000 externally but this is a chromebook issue.
We did run into issues with the current agent.cfg paths for the agent.xml file and the stylesheet settings.
Current settings and suggested changes to the agent.cfg file:

# note only the relevant lines are shown
Devices = /data/agent/agent.xml   # Original - note the docker-compose.yaml mounts to:
#  volumes:
#       - ../setups/$SETUP/volumes/agent:/mtconnect/config # should have agent.cfg, agent.xml
# This worked for us:
Devices = ./agent.xml
# This would likely work too:
Devices = /mtconnect/config/agent.xml

# Under the Stylesheets config:

Path = /etc/mtconnect/styles  # Original 
Path = /mtconnect/data/styles            # new  

 Path = /etc/mtconnect/styles/favicon.ico # Original 
 Path = /mtconnect/data/styles/favicon.ico # new

I'll try an do a pull request, but these are changes we made to get the container/ service running. However the path mismatch might be different for different agent images, so a Dockerfile and a build might be better controlled?
Thanks again for a great complete solution around MTConnect, data persistence and visualisation!

Metadata

Metadata

Assignees

Labels

application:agentAnything related to a specific application

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions