Flowiseai

Stack

AI LLM

Open source UI visual tool to build your customized LLM flow using LangchainJS, written in Node Typescript/Javascript

Configuration

Type

Compose

Platform

linux

Source

Repo

Template by xneo1·Source

Services

flowise-db

Configuration

Image

postgres

Volumes

/var/lib/postgresql/data : /portainer/Files/AppData/Config/flowiseai/db

Env vars

POSTGRES_DB=flowisePOSTGRES_USER=flowiseuserPOSTGRES_PASSWORD=flowisepass

Restart

on-failure

Image details

Pulls: 11.2B

User: stackbrew

Created: Jun 05, 2014

Updated: 1 hour ago

Status: active

flowise

Configuration

Image

flowiseai/flowise:latest

Command

/bin/sh -c "sleep 3; flowise start"

Ports

8459:3000

Volumes

/root/.flowise : /portainer/Files/AppData/Config/data

Env vars

DEBUG=falsePORT=3000FLOWISE_USERNAME=xneo1FLOWISE_PASSWORD=xneo1portainerDATABASE_PATH=/root/.flowiseAPIKEY_PATH=/root/.flowiseSECRETKEY_PATH=/root/.flowiseLOG_LEVEL=infoLOG_PATH=/root/.flowise/logsDATABASE_TYPE=postgresDATABASE_PORT=5432DATABASE_HOST=flowise-dbDATABASE_NAME=flowiseDATABASE_USER=flowiseuserDATABASE_PASSWORD=flowisepass

Restart

on-failure

Image details

Pulls: 6.8M

User: flowiseai

Created: Apr 10, 2023

Updated: 15 days ago

Status: active

Standalone Install

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

Installation method

Docker Run

Docker Compose

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

Ensure both Docker and Portainer are installed, and up-to-date
Log into your Portainer web UI
Under Settings → App Templates, paste the below URL
Head to Home → App Templates, and the list of apps will show up
Select Flowiseai, fill in any config options, and hit Deploy

Template Import URL

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

Show Me

Original stackfile

The compose file this template deploys, straight from its repo:

services:
  flowise-db:
    image: postgres
    container_name: FlowiseAI-DB
    hostname: flowise-db
    mem_limit: 1g
    cpu_shares: 768
    security_opt:
      - no-new-privileges:true
    healthcheck:
      test: ["CMD", "pg_isready", "-q", "-d", "flowise", "-U", "flowiseuser"]
      timeout: 45s
      interval: 10s
      retries: 10
    volumes:
      - /portainer/Files/AppData/Config/flowiseai/db:/var/lib/postgresql/data:rw
    environment:
      POSTGRES_DB: flowise
      POSTGRES_USER: flowiseuser
      POSTGRES_PASSWORD: flowisepass
    restart: on-failure

  flowise:
    image: flowiseai/flowise:latest
    command: /bin/sh -c "sleep 3; flowise start"
    container_name: FlowiseAI
    hostname: flowise
    mem_limit: 4g
    cpu_shares: 768
    security_opt:
      - no-new-privileges:true
    healthcheck:
      test: wget --no-verbose --tries=1 --spider http://localhost:3000
    ports:
      - 8459:3000
    volumes:
      - /portainer/Files/AppData/Config/data:/root/.flowise:rw
    environment:
      DEBUG: false
      PORT: 3000
      FLOWISE_USERNAME: xneo1
      FLOWISE_PASSWORD: xneo1portainer
      DATABASE_PATH: /root/.flowise
      APIKEY_PATH: /root/.flowise
      SECRETKEY_PATH: /root/.flowise
      LOG_LEVEL: info
      LOG_PATH: /root/.flowise/logs
      DATABASE_TYPE: postgres
      DATABASE_PORT: 5432
      DATABASE_HOST: flowise-db
      DATABASE_NAME: flowise
      DATABASE_USER: flowiseuser
      DATABASE_PASSWORD: flowisepass
    restart: on-failure
    depends_on:
      flowise-db:
        condition: service_healthy

Or deploy it directly from the source:

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

More install options in our documentation.

Container Documentation

flowise-db Documentation

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

flowise Documentation

Low-code developer tool for building LLM Applications

Serve Flowiseai 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.

Proxy Domain App port Upstream

Proxying flowiseai.example.com to http://flowise:3000

Add this to your Caddyfile

flowiseai.example.com {
	reverse_proxy http://flowise: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 <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:8459 failed: port is already allocated", something else on your server is using that port.

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

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/flowiseai/db (and the same for the other mapped folders)

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.

Bug within the app: Open an issue within flowiseai's repo
Template not working: Open an issue on xneo1/portainer_templates
This website not working: Open an issue on lissy93/portainer-templates

A Compose stack

Flowiseai 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:

flowise-db runs postgres
flowise runs flowiseai/flowise:latest, starts after flowise-db

Ports

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

8459:3000, likely the web interface

Volumes

A volume is where Flowiseai 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/flowiseai/db on the host
/root/.flowise from /portainer/Files/AppData/Config/data on the host

Environment variables

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

POSTGRES_DB, defaults to flowise
POSTGRES_USER, defaults to flowiseuser
POSTGRES_PASSWORD, defaults to flowisepass
DEBUG, defaults to false
PORT, defaults to 3000
FLOWISE_USERNAME, defaults to xneo1
FLOWISE_PASSWORD, defaults to xneo1portainer
DATABASE_PATH, defaults to /root/.flowise
APIKEY_PATH, defaults to /root/.flowise
SECRETKEY_PATH, defaults to /root/.flowise
LOG_LEVEL, defaults to info
LOG_PATH, defaults to /root/.flowise/logs
DATABASE_TYPE, defaults to postgres
DATABASE_PORT, defaults to 5432
DATABASE_HOST, defaults to flowise-db
DATABASE_NAME, defaults to flowise
DATABASE_USER, defaults to flowiseuser
DATABASE_PASSWORD, defaults to flowisepass

Restart policy

The restart policy here is on-failure, so Flowiseai only gets restarted when it exits with an error, not when it finishes cleanly or you stop it yourself. 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

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

Flowiseai

Configuration

Services

flowise-db

Configuration

Image details

flowise

Configuration

Image details

Standalone Install

Install on Portainer

Template Import URL

Container Documentation

flowise-db Documentation

flowise Documentation

Proxy configurator

Troubleshooting

Check the logs first

Port already in use

Running but the page won't load

Permission denied on volumes

Image won't pull

"exec format error"

Stack won't deploy

Raise an issue

Config glossary

A Compose stack

The services

Ports

Volumes

Environment variables

Restart policy

Networking

Platform

Portainer app templates

Similar apps