mirror of
https://github.com/FreshRSS/FreshRSS.git
synced 2025-12-23 21:47:44 -05:00
9c8e9a8b87
Better fix instead of https://github.com/FreshRSS/FreshRSS/pull/8216 Based on error message: Error: in 18+, these Docker images are configured to store database data in a format which is compatible with "pg_ctlcluster" (specifically, using major-version-specific directory names). This better reflects how PostgreSQL itself works, and how upgrades are to be performed. See also https://github.com/docker-library/postgres/pull/1259 Counter to that, there appears to be PostgreSQL data in: /var/lib/postgresql/data (unused mount/volume) This is usually the result of upgrading the Docker image without upgrading the underlying database using "pg_upgrade" (which requires both versions). The suggested container configuration for 18+ is to place a single mount at /var/lib/postgresql which will then place PostgreSQL data in a subdirectory, allowing usage of "pg_upgrade --link" without mount point boundary issues. See https://github.com/docker-library/postgres/issues/37 for a (long) discussion around this process, and suggestions for how to do so.
27 lines
657 B
YAML
27 lines
657 B
YAML
volumes:
|
|
db:
|
|
|
|
services:
|
|
freshrss-db:
|
|
image: postgres:18
|
|
container_name: freshrss-db
|
|
hostname: freshrss-db
|
|
restart: unless-stopped
|
|
logging:
|
|
options:
|
|
max-size: 10m
|
|
volumes:
|
|
- db:/var/lib/postgresql
|
|
environment:
|
|
POSTGRES_DB: ${DB_BASE:-freshrss}
|
|
POSTGRES_USER: ${DB_USER:-freshrss}
|
|
POSTGRES_PASSWORD: ${DB_PASSWORD:-freshrss}
|
|
command:
|
|
# Examples of PostgreSQL tuning.
|
|
# https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server
|
|
# When in doubt, skip and stick to default PostgreSQL settings.
|
|
- -c
|
|
- shared_buffers=1GB
|
|
- -c
|
|
- work_mem=32MB
|