-
-
Notifications
You must be signed in to change notification settings - Fork 149
Open
Labels
Description
Summary
I have an error message in my PG container, when the backup is running, and also there are errors in the backup container - see below for the errors
I am running other database containers (also PG, but no Timescale DB there) and those are running without issues (same image version).
Steps to reproduce
Part of my docker-compose:
timescaledb:
image: timescale/timescaledb:latest-pg17
container_name: timescaledb
restart: always
security_opt:
- no-new-privileges:true
healthcheck:
test: ["CMD-SHELL", "pg_isready -U pguser -d pgdatabase"]
interval: 5s
timeout: 5s
retries: 5
networks:
- default
environment:
POSTGRES_DB: pgdatabase
POSTGRES_USER: pguser
POSTGRES_PASSWORD: pguserpw
TZ: Europe/Berlin
volumes:
- /etc/localtime:/etc/localtime:ro
- ./pgsql-data:/var/lib/postgresql/data
timescaledb-backup:
image: tiredofit/db-backup
container_name: timescaledb-backup
restart: always
security_opt:
- no-new-privileges:true
environment:
- DB01_TYPE=pgsql
- DB01_HOST=timescaledb
- DB01_NAME=pgdatabase
- DB01_USER=pguser
- DB01_PASS=pguserpw
- DEFAULT_BACKUP_BEGIN=0300
- DEFAULT_BACKUP_INTERVAL=1440
- DEFAULT_CLEANUP_TIME=8640
- DEFAULT_COMPRESSION=GZ
- DEFAULT_COMPRESSION_LEVEL=9
- DEFAULT_CREATE_LATEST_SYMLINK=FALSE
- DEFAULT_FILESYSTEM_PATH_PERMISSION=755
- DEFAULT_FILESYSTEM_PERMISSION=644
- CONTAINER_ENABLE_MONITORING=FALSE
- TZ=Europe/Berlin
volumes:
- /etc/localtime:/etc/localtime:ro
- ./backups:/backup
depends_on:
- timescaledb
networks:
- default
What is the expected correct behavior?
Obviously no errors or issues.
Relevant logs and/or screenshots
Error messages in the PG container:
2025-08-30 03:00:01.136 CEST [275527] FATAL: password authentication failed for user "dbbackup"
2025-08-30 03:00:01.136 CEST [275527] DETAIL: Role "dbbackup" does not exist.
Connection matched file "/var/lib/postgresql/data/pg_hba.conf" line 128: "host all all all scram-sha-256"
Error messages in the backup container:
pg_dump: warning: there are circular foreign-key constraints on this table:
pg_dump: detail: hypertable
pg_dump: hint: You might not be able to restore the dump without using --disable-triggers or temporarily dropping the constraints.
pg_dump: hint: Consider using a full dump instead of a --data-only dump to avoid this problem.
pg_dump: warning: there are circular foreign-key constraints on this table:
pg_dump: detail: chunk
pg_dump: hint: You might not be able to restore the dump without using --disable-triggers or temporarily dropping the constraints.
pg_dump: hint: Consider using a full dump instead of a --data-only dump to avoid this problem.
pg_dump: warning: there are circular foreign-key constraints on this table:
pg_dump: detail: continuous_agg
pg_dump: hint: You might not be able to restore the dump without using --disable-triggers or temporarily dropping the constraints.
pg_dump: hint: Consider using a full dump instead of a --data-only dump to avoid this problem.
Environment
- Image version / tag: latest version
- Host OS: Debian 13