Portainer Templates logo

Portainer Templates

Litmus Edge Digital Factory Demo Litmus Edge Digital Factory Demo

Stack

edge

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.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by portainer·Source

Services

le

Configuration

Image
litmusedge.azurecr.io/litmusedge-std-docker:latest
Ports
8443:4438086:8086
Restart
unless-stopped

simulation_servers

Configuration

Image
litmusedge.azurecr.io/litmus/simulation_servers:latest
Ports
502-505:502-5054840-4843:4840-4843102-105:102-105
Restart
always

mssql

Configuration

Image
litmusedge.azurecr.io/litmus/demo_mssql:latest
Ports
1433:1433
Restart
always

mysql

Configuration

Image
litmusedge.azurecr.io/litmus/demo_mysql:latest
Ports
3306:3306
Env vars
MYSQL_ROOT_PASSWORD=Demo1234
Restart
always

grafana

Configuration

Image
litmusedge.azurecr.io/litmus/demo_grafana:latest
Ports
3000:3000
Env vars
HOST_IP=172.172.0.1GF_LOG_LEVEL=warn
Restart
always

template-applyer

Configuration

Image
litmusedge.azurecr.io/litmus/template_applyer:latest
Env vars
EDGE_API_TOKEN=initEDGE_URL=172.172.0.1:8443ACTION=ApplyDEPLOYMENT_METHOD=dockerMSSQL_URL=172.172.0.1

Standalone Install

Select an install method, to see config/commands for deploying Litmus Edge Digital Factory Demo

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Litmus Edge Digital Factory Demo, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

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 deploy it directly from the source:

git clone https://github.com/portainer/templates
cd templates
docker compose -f edge/litmusedge_dfd/docker-compose.yml up -d

More install options in our documentation.

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: 137 means killed, usually out of memory. 126 or 127 means 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:443 only 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 login to 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 no so 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.

A Compose stack

Litmus Edge Digital Factory Demo is a Compose stack, a set of containers (6 of them) defined in one file and brought up together by Portainer, then started and stopped as a single app.

The services

This stack is built from 6 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • le runs litmusedge.azurecr.io/litmusedge-std-docker:latest
  • simulation_servers runs litmusedge.azurecr.io/litmus/simulation_servers:latest
  • mssql runs litmusedge.azurecr.io/litmus/demo_mssql:latest
  • mysql runs litmusedge.azurecr.io/litmus/demo_mysql:latest
  • grafana runs litmusedge.azurecr.io/litmus/demo_grafana:latest
  • template-applyer runs litmusedge.azurecr.io/litmus/template_applyer:latest, starts after le

Ports

A port is the door the app answers on. A mapping like 8443:443 means it's reachable on port 8443 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open https://your-server-ip:8443 in a browser. It opens:

  • 8443:443, likely the web interface
  • 8086:8086
  • 502-505:502-505
  • 4840-4843:4840-4843
  • 102-105:102-105
  • 1433:1433
  • 3306:3306
  • 3000:3000, likely the web interface

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Litmus Edge Digital Factory Demo takes 8 of them, all with defaults you can leave alone or tweak:

  • MYSQL_ROOT_PASSWORD, defaults to Demo1234
  • HOST_IP, defaults to 172.172.0.1
  • GF_LOG_LEVEL, defaults to warn
  • EDGE_API_TOKEN, defaults to init
  • EDGE_URL, defaults to 172.172.0.1:8443
  • ACTION, defaults to Apply
  • DEPLOYMENT_METHOD, defaults to docker
  • MSSQL_URL, defaults to 172.172.0.1

Restart policy

The restart policy here is unless-stopped, so Docker restarts Litmus Edge Digital Factory Demo after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like le) while only the ports above are open to you.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Litmus Edge Digital Factory Demo up. Add the template list to Portainer once, then deploying Litmus Edge Digital Factory Demo is a click rather than a wall of config.