![Litmus Edge Digital Factory Demo]()
Litmus Edge Digital Factory Demo
Demo System for Litmus Edge. Litmus Edge is an edge data platform that enables industrial AI at scale. It connects, processes, and analyzes real-time OT data at the edge to power smart manufacturing. Note: Requires 5GB Disk Space / 3GB RAM available on the Host for deployment to succeed.
Services
le
Configuration
Imagelitmusedge.azurecr.io/litmusedge-std-docker:latest8443:4438086:8086unless-stoppedsimulation_servers
Configuration
Imagelitmusedge.azurecr.io/litmus/simulation_servers:latest502-505:502-5054840-4843:4840-4843102-105:102-105alwaysmssql
Configuration
Imagelitmusedge.azurecr.io/litmus/demo_mssql:latest1433:1433alwaysmysql
Configuration
Imagelitmusedge.azurecr.io/litmus/demo_mysql:latest3306:3306MYSQL_ROOT_PASSWORD=Demo1234alwaysgrafana
Configuration
Imagelitmusedge.azurecr.io/litmus/demo_grafana:latest3000:3000HOST_IP=172.172.0.1GF_LOG_LEVEL=warnalwaystemplate-applyer
Configuration
Imagelitmusedge.azurecr.io/litmus/template_applyer:latestEDGE_API_TOKEN=initEDGE_URL=172.172.0.1:8443ACTION=ApplyDEPLOYMENT_METHOD=dockerMSSQL_URL=172.172.0.1Installation
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select the app you wish to deploy, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Service #1 - le
docker run -d --name le \
-p 8443:443 \
-p 8086:8086 \
--restart=unless-stopped \
litmusedge.azurecr.io/litmusedge-std-docker:latestService #2 - simulation_servers
docker run -d --name simulation_servers \
-p 502-505:502-505 \
-p 4840-4843:4840-4843 \
-p 102-105:102-105 \
--restart=always \
litmusedge.azurecr.io/litmus/simulation_servers:latestService #3 - mssql
docker run -d --name mssql \
-p 1433:1433 \
--restart=always \
litmusedge.azurecr.io/litmus/demo_mssql:latestService #4 - mysql
docker run -d --name mysql \
-p 3306:3306 \
-e 'MYSQL_ROOT_PASSWORD=Demo1234' \
--restart=always \
litmusedge.azurecr.io/litmus/demo_mysql:latestService #5 - grafana
docker run -d --name grafana \
-p 3000:3000 \
-e 'HOST_IP=172.172.0.1' \
-e 'GF_LOG_LEVEL=warn' \
--restart=always \
litmusedge.azurecr.io/litmus/demo_grafana:latestService #6 - template-applyer
docker run -d --name template-applyer \
-e 'EDGE_API_TOKEN=init' \
-e 'EDGE_URL=172.172.0.1:8443' \
-e 'ACTION=Apply' \
-e 'DEPLOYMENT_METHOD=docker' \
-e 'MSSQL_URL=172.172.0.1' \
litmusedge.azurecr.io/litmus/template_applyer:latest
If the stack expects env vars, set them or add them to a .env file first.
networks:
devices:
driver: bridge
driver_opts:
com.docker.network.enabled_ipv6: "false"
ipam:
driver: default
config:
- subnet: 172.172.0.0/24
services:
le:
image: litmusedge.azurecr.io/litmusedge-std-docker:latest
container_name: dfd-le
networks:
devices:
ipv4_address: 172.172.0.2
ports:
- "8443:443"
- "8086:8086"
restart: unless-stopped
simulation_servers:
image: litmusedge.azurecr.io/litmus/simulation_servers:latest
networks:
devices:
ipv4_address: 172.172.0.5
ports:
- "502-505:502-505"
- "4840-4843:4840-4843"
- "102-105:102-105"
restart: always
logging:
driver: "json-file"
options:
max-size: "50m"
mssql:
image: litmusedge.azurecr.io/litmus/demo_mssql:latest
ports:
- "1433:1433"
networks:
devices:
ipv4_address: 172.172.0.50
labels:
- networks=bridge
restart: always
logging:
driver: "json-file"
options:
max-size: "10m"
mysql:
image: litmusedge.azurecr.io/litmus/demo_mysql:latest
ports:
- "3306:3306"
networks:
devices:
ipv4_address: 172.172.0.49
environment:
MYSQL_ROOT_PASSWORD: Demo1234
restart: always
logging:
driver: "json-file"
options:
max-size: "10m"
grafana:
image: litmusedge.azurecr.io/litmus/demo_grafana:latest
environment:
HOST_IP: 172.172.0.1
GF_LOG_LEVEL: warn
ports:
- "3000:3000"
user: 0:0
networks:
devices:
ipv4_address: 172.172.0.51
labels:
- networks=bridge
restart: always
logging:
driver: "json-file"
options:
max-size: "10m"
template-applyer:
image: litmusedge.azurecr.io/litmus/template_applyer:latest
environment:
- EDGE_API_TOKEN=init
- EDGE_URL=172.172.0.1:8443
- ACTION=Apply
- DEPLOYMENT_METHOD=docker
- MSSQL_URL=172.172.0.1
depends_on:
- le
Or, use the original compose file, straight from the template repo. Deploy with:
git clone https://github.com/portainer/templates
cd templates
docker compose -f edge/litmusedge_dfd/docker-compose.yml up -d
For more installation options, see the Documentation in our GitHub repo
Serve Litmus Edge Digital Factory Demo on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying litmus-edge-digital-factory-demo.example.com to https://le:443
Add this to your Caddyfile
litmus-edge-digital-factory-demo.example.com {
reverse_proxy https://le:443 {
transport http {
tls_insecure_skip_verify
}
}
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs <container> - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:8443 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :8443 - Stop the other service, or pick a different host port. In
8443:443only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
https://your-server-ip:8443. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, le can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 8443
Image won't pull
Test the pull directly on the host: docker pull litmusedge.azurecr.io/litmusedge-std-docker:latest
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Container keeps restarting
The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.
- Check the logs right after a restart, the last few lines before it died are the useful ones.
- Get the exit code with
docker inspect <container> --format '{{.State.ExitCode}}' - Still stuck? Redeploy once with the restart policy set to
noso the failure stays visible.
Stack won't deploy
Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.
- YAML only accepts spaces for indentation, a single tab breaks the whole file.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within le's repo
- Template not working: Open an issue on portainer/templates
- This website not working: Open an issue on lissy93/portainer-templates