Portainer Templates logo

Portainer Templates

SORBA SDE SORBA SDE

Stack

edge

The SORBA Smart Data Engine (SDE) is an industrial data collection/gateway device capable of Advanced Edge Analytics & Machine Learning Edge Processing. SORBA-SDE is equipped with multiple communication driver/protocol applicable to the industrial market. The SORBA-SDE is a sensor/hardware agnostic device that serves as your point & click gateway capable of talking to multiple devices in real-time. The SDE provides easy access to equipment for troubleshooting and remote programming support for PLCs & HMIs utilizing a hassle-free easy, set-up approach to your assets.

Image details

Pulls: 26.9k
Architecture: amd64
Image size: 8.7 GB
Latest: 10.7.9
User: sorbotics
Created: Dec 21, 2023
Updated: 8 days ago
Status: active

Configuration

Type
Compose
Platform
linux
Image
sorbotics/sorba-sde:latest
Ports
443:443/tcp502:502/tcp1883:1883/tcp49321:49321/tcp
Volumes
/opt : sde-volume
Restart
always
Source
Repo

Template by portainer·Source

Standalone Install

Select an install method, to see config/commands for deploying SORBA SDE

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 SORBA SDE, 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:

services:
  sde:
    image: sorbotics/sorba-sde:latest
    container_name: my-sde
    cap_add:
      - NET_ADMIN
    restart: always
    volumes:
      - sde-volume:/opt
    ports:
      - 443:443/tcp
      - 502:502/tcp
      - 1883:1883/tcp
      - 49321:49321/tcp
    sysctls:
      - net.ipv4.ip_forward=1
    networks:
      - sorbotics

volumes:
  sde-volume:
    driver: local

networks:
  sorbotics:

Or deploy it directly from the source:

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

More install options in our documentation.

SORBA Smart Data Engine

See more at https://help.sorbotics.com

Serve SORBA SDE 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 sorba-sde.example.com to https://sde:443

Add this to your Caddyfile

sorba-sde.example.com {
	reverse_proxy https://sde: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:443 failed: port is already allocated", something else on your server is using that port.

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

Image won't pull

Test the pull directly on the host: docker pull sorbotics/sorba-sde: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.

  • This image supports: amd64
  • 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 always 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

SORBA SDE is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything SORBA SDE needs bundled into one download. This template pulls sorbotics/sorba-sde:latest, which Docker fetches once (about 8.7 GB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. SORBA SDE's comes from Docker Hub, published by sorbotics.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 10.7.9. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, so it runs on regular x86 PCs and servers, though not ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 443:443 means it's reachable on port 443 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:443 in a browser. It opens:

  • 443:443, likely the web interface
  • 502:502
  • 1883:1883
  • 49321:49321

Volumes

A volume is where SORBA SDE keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /opt kept in the sde-volume volume Docker manages

Restart policy

The restart policy here is always, so Docker brings SORBA SDE back up after a crash and again when the server reboots. Good for anything you want running around the clock. 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

Nothing custom is set, so SORBA SDE sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container sde. That's what you'll spot in the containers list and use in commands like docker logs sde.

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 SORBA SDE up. Add the template list to Portainer once, then deploying SORBA SDE is a click rather than a wall of config.