![Teable]()
Teable
Stack
Spreadsheet-style database in the vein of Airtable, built on Postgres: grid, kanban, calendar, gallery and form views, file attachments, formulas, real-time collaboration and an API. Source: https://github.com/teableio/teable
Source details
Configuration
TypeComposelinuxTEABLE_SECRET=''TEABLE_DB_PASSWORD=''TEABLE_URL=http://localhost:3500TEABLE_PORT=3500unless-stoppedTemplate by NotAFlightRisk·Source
Report issueNotes
http://<your-host>:3500 (or whichever port you picked). The first account you sign up becomes the admin. Anyone who can reach it can sign up after that, so once you're in, switch off Allow creating new accounts under System Admin --> Instance settings. Set the address field to wherever you'll open it, or invite links will point at localhost. Teable's image sends a small daily usage report to Teable (your instance ID, how many people are active, and a rough count of spaces and bases). To stop it, add TEABLE_TELEMETRY_OFF set to true to the stack's environment variables and redeploy. AI features and enterprise extras need a paid licence, everything else is free. Attachments live in the teable-data volume, logins in teable-cache, and your tables in postgres-data. Docs: help.teable.aiServices
teable
Configuration
Imageghcr.io/teableio/teable:latest${TEABLE_PORT:-3500}:3000/app/.assets : teable-data/data : teable-cachePUBLIC_ORIGIN=${TEABLE_URL:-http://localhost:3500}SECRET_KEY=${TEABLE_SECRET:?Set a secret key}PRISMA_DATABASE_URL=postgresql://teable:${TEABLE_DB_PASSWORD:?Set a database password}@postgres:5432/teableTELEMETRY_REPORT_DISABLED=${TEABLE_TELEMETRY_OFF:-false}unless-stoppedImage details
postgres
Configuration
Imagepostgres:17-alpine/var/lib/postgresql/data : postgres-dataPOSTGRES_DB=teablePOSTGRES_USER=teablePOSTGRES_PASSWORD=${TEABLE_DB_PASSWORD:?Set a database password}unless-stoppedImage details
Standalone Install
Select an install method, to see config/commands for deploying Teable
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 Teable, 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:
teable:
image: ghcr.io/teableio/teable:latest
restart: unless-stopped
ports:
- "${TEABLE_PORT:-3500}:3000"
environment:
PUBLIC_ORIGIN: ${TEABLE_URL:-http://localhost:3500}
SECRET_KEY: ${TEABLE_SECRET:?Set a secret key}
PRISMA_DATABASE_URL: postgresql://teable:${TEABLE_DB_PASSWORD:?Set a database password}@postgres:5432/teable
TELEMETRY_REPORT_DISABLED: ${TEABLE_TELEMETRY_OFF:-false}
volumes:
- teable-data:/app/.assets
- teable-cache:/data
depends_on:
postgres:
condition: service_healthy
postgres:
image: postgres:17-alpine
restart: unless-stopped
environment:
POSTGRES_DB: teable
POSTGRES_USER: teable
POSTGRES_PASSWORD: ${TEABLE_DB_PASSWORD:?Set a database password}
volumes:
- postgres-data:/var/lib/postgresql/data
healthcheck:
test: ["CMD-SHELL", "pg_isready -U teable -d teable"]
interval: 10s
timeout: 5s
retries: 5
volumes:
teable-data:
teable-cache:
postgres-data:
Or deploy it directly from the source:
git clone https://github.com/NotAFlightRisk/portainer-templates-extras
cd portainer-templates-extras
docker compose -f apps/teable/compose.yml up -dMore install options in our documentation, or see teableio/teable for app-specific guidance.
Container Documentation
postgres Documentation
The PostgreSQL object-relational database system provides reliability and data integrity.
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:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Image won't pull
Test the pull directly on the host: docker pull ghcr.io/teableio/teable:latest
- "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 loginto 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
noso 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.
- Bug within the app: Open an issue on teableio/teable
- Template not working: Open an issue on NotAFlightRisk/portainer-templates-extras
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
Teable 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:
teablerunsghcr.io/teableio/teable:latest, starts after postgrespostgresrunspostgres:17-alpine
Volumes
A volume is where Teable 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:
/app/.assetskept in theteable-datavolume Docker manages/datakept in theteable-cachevolume Docker manages/var/lib/postgresql/datakept in thepostgres-datavolume Docker manages
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Teable takes 7 of them, and 2 need a value before it'll start properly:
PUBLIC_ORIGIN, defaults tohttp://localhost:3500SECRET_KEY, needs a valuePRISMA_DATABASE_URL, defaults topostgresql://teable:@postgres:5432/teableTELEMETRY_REPORT_DISABLED, defaults tofalsePOSTGRES_DB, defaults toteablePOSTGRES_USER, defaults toteablePOSTGRES_PASSWORD, needs a value
Restart policy
The restart policy here is unless-stopped, so Docker restarts Teable 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 teable) 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 Teable up. Add the template list to Portainer once, then deploying Teable is a click rather than a wall of config.