Portainer Templates logo

Portainer Templates

Huginn Huginn

Container

OtherTools

Create agents that monitor and act on your behalf.

Image details

Pulls: 2k
Architecture: arm64, arm
Image size: 610 MB
User: mjysci
Created: Dec 22, 2020
Updated: 2 years ago
Status: active

Configuration

Type
Container
Platform
linux
Image
mjysci/huginn:arm32v7
Ports
3005:3000/tcp
Volumes
/var/lib/mysql : /portainer/Files/AppData/Config/huginn
Restart
unless-stopped

Template by novaspirit

Notes

Template created by Pi-Hosted Series
Check our Github page: https://github.com/pi-hosted/pi-hosted

Official Webpage: https://github.com/huginn/huginn
Official Docker Documentation: https://github.com/huginn/huginn/tree/master/docker


Standalone Install

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

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 Huginn, fill in any config options, and hit Deploy

Template Import URL

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

More install options in our documentation.

arm64v8 aarch64

NOTICE: This is still in the testing phase. If the arm32v7 tag fits your requirements, then stick with it.
It works fine on a 2GB Raspberry Pi 4B, but is barely usable on a 1GB Raspberry Pi 3B.
There's an issue with MySQL internally, so you'll need to connect to mysql or postgres externally.
docker network create huginn

docker run -d --name huginn-db \
  -p 3306:3306 \
  --network huginn \
  --network-alias mysql \
  -v /opt/docker/huginn/data:/var/lib/mysql \
  -e MYSQL_ROOT_PASSWORD=somethingevenmoresecret \
  -e MYSQL_DATABASE=huginn_production \
  -e MYSQL_USER=huginn \
  -e MYSQL_PASSWORD=somethingsecret  \
  mysql:8.0

docker run -d --name huginn \
    --network huginn \
    -p 3000:3000 \
    -e DATABASE_ADAPTER=mysql2 \
    -e DATABASE_HOST=mysql \
    -e DATABASE_PORT=3306 \
    -e DATABASE_NAME=huginn_production \
    -e DATABASE_USERNAME=huginn \
    -e DATABASE_PASSWORD=somethingsecret \
    mjysci/huginn:dev

The single process one is more stable.

arm32v7

docker volume create huginn-data
docker run -d --name huginn --restart=on-failure:5 -p 3000:3000 -v huginn-data:/var/lib/mysql mjysci/huginn:arm32v7
This one is also compatible with aarch64 (arm64v8) devices.
For further usage instructions, you can check here.

Serve Huginn 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 huginn.example.com to http://huginn:3000

Add this to your Caddyfile

huginn.example.com {
	reverse_proxy http://huginn:3000
}

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

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

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/huginn

Image won't pull

Test the pull directly on the host: docker pull mjysci/huginn:arm32v7

  • "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: arm64, arm
  • 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 huginn --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Huginn runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Huginn needs bundled into one download. This template pulls mjysci/huginn:arm32v7, which Docker fetches once (about 610 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. Huginn's comes from Docker Hub, published by mjysci.

Version tags

The bit after the colon in the image name is the version tag. This one pins arm32v7, 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 arm64, arm, so it runs on ARM boards like a Raspberry Pi, but not regular x86 servers.

Ports

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

  • 3005:3000, likely the web interface

Volumes

A volume is where Huginn 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/lib/mysql from /portainer/Files/AppData/Config/huginn on the host

Restart policy

The restart policy here is unless-stopped, so Docker restarts Huginn 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

Nothing custom is set, so Huginn 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 huginn. That's what you'll spot in the containers list and use in commands like docker logs huginn.

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