Portainer Templates logo

Portainer Templates

MaestroHub MaestroHub

edge

Industrial data orchestrator with a Unified Namespace, drag-and-drop pipelines, and 40+ protocol connectors. Built-in MCP server brings AI agents into your operational data stack.

Configuration

Type
Compose
Platform
linux
Image
us-docker.pkg.dev/maestrohubtests/maestrohub/maestrohub-lite:latest
Ports
8080:80801883:18838083:8083
Volumes
/data : maestrohub-data
Restart
unless-stopped
Source
Repo

Template by portainer·Source

Notes

Welcome to MaestroHub! • Open http://<host>:8080 to create your admin account • MQTT clients can connect to <host>:1883 (TCP) or <host>:8083 (WebSocket) • Data persists in the maestrohub-data Docker volume — back it up before destroying the stack • Get started guide: https://docs.maestrohub.com/overview/get-started

Installation

  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 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 demo

docker run -d --name maestrohub \
  -p 8080:8080 \
  -p 1883:1883 \
  -p 8083:8083 \
  -v maestrohub-data:/data \
  --restart=unless-stopped \
  us-docker.pkg.dev/maestrohubtests/maestrohub/maestrohub-lite:latest

If the stack expects env vars, set them or add them to a .env file first.

services:
  maestrohub:
    image: us-docker.pkg.dev/maestrohubtests/maestrohub/maestrohub-lite:latest
    container_name: maestrohub
    restart: unless-stopped
    ports:
      - "8080:8080"
      - "1883:1883"
      - "8083:8083"
    volumes:
      - maestrohub-data:/data

volumes:
  maestrohub-data:

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/maestrohub/docker-compose.yml up -d

Save this file as maestrohub-stack.yml, then from a manager node, run docker stack deploy -c maestrohub-stack.yml maestrohub

version: '3.8'
services:
  maestrohub:
    image: us-docker.pkg.dev/maestrohubtests/maestrohub/maestrohub-lite:latest
    ports:
      - '8080:8080'
      - '1883:1883'
      - '8083:8083'
    volumes:
      - maestrohub-data:/data
    deploy:
      restart_policy:
        condition: any

Save each file below into a folder, then run kubectl apply -f .
Written for k3s, but works on any cluster: bind mounts use hostPath, named volumes get a persistent volume claim, and ports are exposed via a LoadBalancer service.

maestrohub-deployment.yaml

apiVersion: apps/v1
kind: Deployment
metadata:
  name: maestrohub
  labels:
    app: maestrohub
spec:
  replicas: 1
  selector:
    matchLabels:
      app: maestrohub
  template:
    metadata:
      labels:
        app: maestrohub
    spec:
      containers:
        - name: maestrohub
          image: us-docker.pkg.dev/maestrohubtests/maestrohub/maestrohub-lite:latest
          ports:
            - containerPort: 8080
              protocol: TCP
            - containerPort: 1883
              protocol: TCP
            - containerPort: 8083
              protocol: TCP
          volumeMounts:
            - name: maestrohub-data-0
              mountPath: /data
      volumes:
        - name: maestrohub-data-0
          hostPath:
            path: maestrohub-data

maestrohub-service.yaml

apiVersion: v1
kind: Service
metadata:
  name: maestrohub
spec:
  type: LoadBalancer
  selector:
    app: maestrohub
  ports:
    - name: 8080-tcp
      port: 8080
      targetPort: 8080
      protocol: TCP
    - name: 1883-tcp
      port: 1883
      targetPort: 1883
      protocol: TCP
    - name: 8083-tcp
      port: 8083
      targetPort: 8083
      protocol: TCP

Save this file as ~/.config/containers/systemd/maestrohub.container

[Unit]
Description=MaestroHub

[Container]
Image=us-docker.pkg.dev/maestrohubtests/maestrohub/maestrohub-lite:latest
ContainerName=maestrohub
PublishPort=8080:8080
PublishPort=1883:1883
PublishPort=8083:8083
Volume=maestrohub-data:/data

[Service]
Restart=always

[Install]
WantedBy=default.target

Then reload systemd and start the service:

systemctl --user daemon-reload
systemctl --user start maestrohub

For a system-wide service, use /etc/containers/systemd/ and drop --user.

For more installation options, see the Documentation in our GitHub repo

Serve MaestroHub 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 maestrohub.example.com to http://maestrohub:8080

Add this to your Caddyfile

maestrohub.example.com {
	reverse_proxy http://maestrohub:8080
}

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:8080 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :8080
  • Stop the other service, or pick a different host port. In 8080:8080 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: http://your-server-ip:8080. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, maestrohub can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8080

Image won't pull

Test the pull directly on the host: docker pull us-docker.pkg.dev/maestrohubtests/maestrohub/maestrohub-lite: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.

Similar apps

Anyviz Cloud Adaptor Anyviz Cloud Adaptor edge CockroachDB (stack) edgeEMQX Open Source MQTT Broker EMQX Open Source MQTT Broker edgeFloating License Server Floating License Server edgeGrafana Dashboard Grafana Dashboard edgeInductive Automation - Ignition Gateway Inductive Automation - Ignition Gateway edgeInfluxDB for Edge InfluxDB for Edge edgeLitmus Edge Litmus Edge edge