Portainer Templates logo

Portainer Templates

Manubes Edge Node Manubes Edge Node

Stack

edge

High-performance cloud platform for industrial production management. Manubes is a no-code solution that is used to structure, monitor and control production data, systems and processes in the cloud.

Image details

Pulls: 3k
Architecture: amd64, arm64, arm/v7
Image size: 232 MB
User: haukemarquardt
Created: May 22, 2024
Updated: 2 days ago
Status: active

Configuration

Type
Compose
Platform
linux
Image
inray/manubes-edge:preview
Command
${MANUBES_SECRET}
Volumes
/var/run/docker.sock : /var/run/docker.sock/data : manubes-data
Env vars
ACCEPT_EULA=${ACCEPT_EULA}MANUBES_SECRET=''
Restart
always
Source
Repo

Template by portainer·Source

Standalone Install

Select an install method, to see config/commands for deploying Manubes Edge Node

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 Manubes Edge Node, 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:

version: '3'

services:
  manubes-edge-node:
    image: inray/manubes-edge:preview
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - manubes-data:/data
    restart: always
    environment:
      ACCEPT_EULA: ${ACCEPT_EULA}
    command: ${MANUBES_SECRET}

volumes:
  manubes-data:

Or deploy it directly from the source:

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

More install options in our documentation.

manubes Edge Node

High-performance cloud platform for industrial production management. manubes is a no-code solution that is used to structure, monitor and control production data, systems and processes in the cloud.

Visit https://manubes.com for more details.

Besuchen Sie https://manubes.de für weitere Informationen.

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.

Can't reach the Docker socket

manubes-edge-node talks to Docker through /var/run/docker.sock. If the logs show "permission denied while trying to connect to the Docker daemon socket", the app's user can't access it.

  • Check the socket exists on the host: ls -l /var/run/docker.sock
  • Run the container as root, or add the docker group's id to the container with group_add.

Image won't pull

Test the pull directly on the host: docker pull inray/manubes-edge:preview

  • "manifest unknown" means the tag no longer exists.
  • "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, arm64, arm/v7
  • 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.

Required settings are blank

MANUBES_SECRET has no default value, and manubes-edge-node may crash or misbehave if left empty.

  • Fill it in on the deploy screen before hitting deploy.

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

Manubes Edge Node 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 Manubes Edge Node needs bundled into one download. This template pulls inray/manubes-edge:preview, which Docker fetches once (about 232 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Manubes Edge Node's comes from Docker Hub, published by inray.

Version tags

The bit after the colon in the image name is the version tag. This one pins preview, so every redeploy gives you that exact build until you bump it yourself.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Volumes

A volume is where Manubes Edge Node 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:

  • /var/run/docker.sock from /var/run/docker.sock on the host (a socket it talks to, not storage)
  • /data kept in the manubes-data volume Docker manages

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Manubes Edge Node takes 2 of them, and one needs a value before it'll start properly:

  • ACCEPT_EULA, pick one of true. Accept EULA
  • MANUBES_SECRET, needs a value. Manubes secret

Restart policy

The restart policy here is always, so Docker brings Manubes Edge Node 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 Manubes Edge Node 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 manubes-edge-node. That's what you'll spot in the containers list and use in commands like docker logs manubes-edge-node.

Startup command

The command is what runs the moment the container starts. This template sets its own, ${MANUBES_SECRET}, in place of the image's default.

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