Self-host PostgreSQL with Levelrail

The PostgreSQL relational database server on the official Alpine image, with a persistent volume and a generated password. It is not published on the host, so reach it from other services in this project at postgres:5432.

  • Authorpostgres
  • LicencePostgreSQL
  • Memory256 MiB
  • Services1

How to self-host PostgreSQL

  1. Pull the images

    One image is pulled on your server.

    Show images
    • postgres:17.11-alpine
  2. Create the app

    One service starts in a single Compose app, with 1 named volume mount for your data, on port 5432.

  3. Fill in the secrets

    1 secret is generated and stored encrypted, 2 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

After the first start

  • Read the generated password from the app secrets, then connect with psql or any client from a service in the same project.

PostgreSQL requirements

Memory
About 256 MiB
Architectures
amd64 unknown, arm64 unknown
Ports
5432
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
PostgreSQL, permissive license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then PostgreSQL. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the PostgreSQL docs page.

Deploy PostgreSQL your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy PostgreSQL from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain postgres=app.example.com.

levelrail-cli templates install postgres --name my-postgres

Deploy PostgreSQL with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/postgres/install \
  -d '{
    "name": "my-postgres"
  }'

PostgreSQL configuration

PostgreSQL services

ServiceImagePortsVolumes
postgres postgres:17.11-alpine 5432 pgdata -> /var/lib/postgresql/data

PostgreSQL environment variables

VariableServiceValue
POSTGRES_DB postgres Preset by the template
POSTGRES_PASSWORD postgres Generated at deploy
POSTGRES_USER postgres Preset by the template

Ports and volumes

Ports
5432
Volumes
1 named mount: pgdata -> /var/lib/postgresql/data

PostgreSQL FAQ

How much memory does PostgreSQL need?

The catalog lists about 256 MiB of memory for PostgreSQL.

Does PostgreSQL run on arm64?

For PostgreSQL, arm64 support is not confirmed; amd64 is unknown.

What licence is PostgreSQL under?

PostgreSQL is licensed under PostgreSQL, which is permissive, with few conditions on reuse.

Does PostgreSQL need configuration before it starts?

No. The template fills in its own defaults and generates secrets at deploy time.

Which database does PostgreSQL bundle?

The template includes Postgres, running as part of the stack.

Which ports does PostgreSQL use?

PostgreSQL listens on port 5432 inside the stack.

Where does PostgreSQL keep its data?

In a named volume: pgdata mounted at /var/lib/postgresql/data.

Can I deploy PostgreSQL on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for PostgreSQL, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image postgres:17.11-alpine is what you deploy there.

levelrail-cli templates install postgres --name my-postgres