Portainer Templates logo

Portainer Templates

Logto Logto

Stack

Auth API Gateway

Logto - the open-source Auth0 experience: pre-built hosted sign-in pages, OIDC/OAuth, social logins, organizations, MFA, and clean SDKs for every framework. MPL-2.0, one container + a managed Postgres.

Configuration

Type
Compose
Platform
linux
Env vars
ADMIN_ENDPOINT=http://localhost:5001ENDPOINT=http://localhost:5000
Source
Repo

Template by deployable-sh·Source

Report issue

Services

logto

Configuration

Ports
5000:50003002
Env vars
DB_URL=postgresql://logto:logto-local-only@db:5432/logtoADMIN_PORT=3002ENDPOINT=${ENDPOINT:-http://localhost:5000}ADMIN_ENDPOINT=${ADMIN_ENDPOINT:-http://localhost:5001}TRUST_PROXY_HEADER=1
Restart
unless-stopped
Build
./core

web-admin

Configuration

Ports
5001:5000
Env vars
PROXY_TARGET=http://logto:3002
Restart
unless-stopped
Build
./proxy

db

Configuration

Image
postgres:17
Ports
5432
Volumes
/var/lib/postgresql/data : dbdata
Env vars
POSTGRES_USER=logtoPOSTGRES_PASSWORD=logto-local-onlyPGDATA=/var/lib/postgresql/data/pgdataPOSTGRES_DB=logto
Restart
unless-stopped

Image details

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

Standalone Install

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

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 Logto, 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:

name: logto

services:
  logto:
    build: ./core
    restart: unless-stopped
    environment:
      DB_URL: postgresql://logto:logto-local-only@db:5432/logto
      ADMIN_PORT: "3002"
      ENDPOINT: ${ENDPOINT:-http://localhost:5000}
      ADMIN_ENDPOINT: ${ADMIN_ENDPOINT:-http://localhost:5001}
      TRUST_PROXY_HEADER: "1"
    ports:
      - "5000:5000"
      - "3002"
    depends_on:
      - db

  web-admin:
    build: ./proxy
    restart: unless-stopped
    environment:
      PROXY_TARGET: http://logto:3002
    ports:
      - "5001:5000"
    depends_on:
      - logto

  db:
    ports:
    - "5432"
    image: postgres:17
    restart: unless-stopped
    environment:
      POSTGRES_USER: logto
      POSTGRES_PASSWORD: logto-local-only
      PGDATA: /var/lib/postgresql/data/pgdata
      POSTGRES_DB: logto
    volumes:
      - dbdata:/var/lib/postgresql/data

volumes:
  dbdata:

Or deploy it directly from the source:

git clone https://github.com/deployable-sh/stacks
cd stacks
docker compose -f logto/compose.yaml up -d

More install options in our documentation.

Container Documentation

db Documentation

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

Serve Logto 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 logto.example.com to http://logto:5000

Add this to your Caddyfile

logto.example.com {
	reverse_proxy http://logto:5000
}

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

  • Find what's using it: sudo ss -tlnp | grep :5000
  • Stop the other service, or pick a different host port. In 5000:5000 only the left number is yours to change, the right one belongs to the app.

Published on a random port

This template exposes 3002 without setting a host port, so Docker picks a random free one on every deploy.

  • Find it in the Ports column of Portainer's container list, or with docker port <container>

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:5000. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, logto can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 5000

Image won't pull

Test the pull directly on the host: docker pull postgres:17

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

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

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

  • logto, starts after db
  • web-admin, starts after logto
  • db runs postgres:17

Ports

A port is the door the app answers on. A mapping like 5000:5000 means it's reachable on port 5000 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 5000:5000
  • 3002, published on a random host port
  • 5001:5000
  • 5432, published on a random host port

Volumes

A volume is where Logto 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 kept in the dbdata volume Docker manages

Environment variables

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

  • DB_URL, defaults to postgresql://logto:logto-local-only@db:5432/logto
  • ADMIN_PORT, defaults to 3002
  • ENDPOINT, defaults to http://localhost:5000
  • ADMIN_ENDPOINT, defaults to http://localhost:5001
  • TRUST_PROXY_HEADER, defaults to 1
  • PROXY_TARGET, defaults to http://logto:3002
  • POSTGRES_USER, defaults to logto
  • POSTGRES_PASSWORD, defaults to logto-local-only
  • PGDATA, defaults to /var/lib/postgresql/data/pgdata
  • POSTGRES_DB, defaults to logto

Restart policy

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

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