Portainer Templates logo

Portainer Templates

Kestra Kestra

Stack

AutomationOrchestration

Powerful orchestration. Simplified workflows.Unify orchestration for all engineers. Build and govern all your workflows — Everything-as-Code, and from the UI.

Configuration

Type
Compose
Platform
linux
Source
Repo

Template by xneo1·Source

Services

kestra-postgres

Configuration

Image
postgres
Volumes
/var/lib/postgresql/data : /portainer/Files/AppData/Config/kestra/postgres-data
Env vars
POSTGRES_DB=kestraPOSTGRES_USER=kestraPOSTGRES_PASSWORD=k3str4

Image details

Pulls: 11.2B
User: stackbrew
Created: Jun 05, 2014
Updated: 1 hour ago
Status: active

kestra

Configuration

Image
kestra/kestra:latest
Command
server standalone
Ports
8080:80808081:8081
Volumes
/app/storage : /portainer/Files/AppData/Config/kestra/kestra-data/var/run/docker.sock : /var/run/docker.sock/tmp/kestra-wd : /portainer/Files/AppData/Config/kestra/kestra-wd
Env vars
KESTRA_CONFIGURATION=datasources: kestra-postgres: url: jdbc:postgresql://postgres:5432/kestra driverClassName: org.postgresql.Driver username: kestra password: k3str4 kestra: server: basicAuth: enabled: false username: "admin@localhost.dev" # it must be a valid email address password: kestra repository: type: postgres storage: type: local local: basePath: "/app/storage" queue: type: postgres tasks: tmpDir: path: /portainer/Files/AppData/Config/kestra/kestra-wd url: http://localhost:8080/

Image details

Pulls: 2.4M
User: kestra
Created: Dec 28, 2019
Updated: 19 hours ago
Status: active

Standalone Install

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

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 Kestra, 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:
  kestra-postgres:
    image: postgres
    volumes:
      - /portainer/Files/AppData/Config/kestra/postgres-data:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: kestra
      POSTGRES_USER: kestra
      POSTGRES_PASSWORD: k3str4
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -d $${POSTGRES_DB} -U $${POSTGRES_USER}"]
      interval: 30s
      timeout: 10s
      retries: 10

  kestra:
    image: kestra/kestra:latest
    pull_policy: always
    # Note that this setup with a root user is intended for development purpose.
    # Our base image runs without root, but the Docker Compose implementation needs root to access the Docker socket
    user: "root"
    command: server standalone
    volumes:
      - /portainer/Files/AppData/Config/kestra/kestra-data:/app/storage
      - /var/run/docker.sock:/var/run/docker.sock
      - /portainer/Files/AppData/Config/kestra/kestra-wd:/tmp/kestra-wd
    environment:
      KESTRA_CONFIGURATION: |
        datasources:
          kestra-postgres:
            url: jdbc:postgresql://postgres:5432/kestra
            driverClassName: org.postgresql.Driver
            username: kestra
            password: k3str4
        kestra:
          server:
            basicAuth:
              enabled: false
              username: "admin@localhost.dev" # it must be a valid email address
              password: kestra
          repository:
            type: postgres
          storage:
            type: local
            local:
              basePath: "/app/storage"
          queue:
            type: postgres
          tasks:
            tmpDir:
              path: /portainer/Files/AppData/Config/kestra/kestra-wd
          url: http://localhost:8080/
    ports:
      - "8080:8080"
      - "8081:8081"
    depends_on:
      kestra-postgres:
        condition: service_started

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/kestra.yml up -d

More install options in our documentation.

Container Documentation

kestra-postgres Documentation

The PostgreSQL object-relational database system provides reliability and data integrity.

kestra Documentation

Kestra is an infinitely scalable orchestration and scheduling platform.

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

Add this to your Caddyfile

kestra.example.com {
	reverse_proxy http://kestra: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, kestra can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 8080

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/kestra/postgres-data (and the same for the other mapped folders)

Can't reach the Docker socket

kestra 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 postgres

  • "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.

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

Kestra is a Compose stack, a set of containers (2 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 2 containers that run side by side. Here's each one, with the image it runs and anything it waits for first:

  • kestra-postgres runs postgres
  • kestra runs kestra/kestra:latest, starts after kestra-postgres

Ports

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

  • 8080:8080, likely the web interface
  • 8081:8081

Volumes

A volume is where Kestra 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/postgresql/data from /portainer/Files/AppData/Config/kestra/postgres-data on the host
  • /app/storage from /portainer/Files/AppData/Config/kestra/kestra-data on the host
  • /var/run/docker.sock from /var/run/docker.sock on the host (a socket it talks to, not storage)
  • /tmp/kestra-wd from /portainer/Files/AppData/Config/kestra/kestra-wd on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Kestra takes 4 of them, all with defaults you can leave alone or tweak:

  • POSTGRES_DB, defaults to kestra
  • POSTGRES_USER, defaults to kestra
  • POSTGRES_PASSWORD, defaults to k3str4
  • KESTRA_CONFIGURATION, defaults to datasources: kestra-postgres: url: jdbc:postgresql://postgres:5432/kestra driverClassName: org.postgresql.Driver username: kestra password: k3str4 kestra: server: basicAuth: enabled: false username: "admin@localhost.dev" # it must be a valid email address password: kestra repository: type: postgres storage: type: local local: basePath: "/app/storage" queue: type: postgres tasks: tmpDir: path: /portainer/Files/AppData/Config/kestra/kestra-wd url: http://localhost:8080/

Networking

Portainer puts these services on one shared private network, so they can find each other by name (like kestra-postgres) 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 Kestra up. Add the template list to Portainer once, then deploying Kestra is a click rather than a wall of config.