Skip to content

Persistent path for database causes Postgres to not start #40

@awils27

Description

@awils27

Following the instructions in the usage area and mounting the storage for postgres and previews i get the following error with postgres when the container starts up:

2025-12-30 14:12:38,466 INFO spawned: 'postgresql' with pid 107
2025-12-30 14:12:38,517 INFO exited: postgresql (exit status 1; not expected)
2025-12-30 14:12:40,520 INFO spawned: 'postgresql' with pid 108
2025-12-30 14:12:40,538 INFO exited: postgresql (exit status 1; not expected)
2025-12-30 14:12:43,543 INFO spawned: 'postgresql' with pid 109
2025-12-30 14:12:43,558 INFO exited: postgresql (exit status 1; not expected)
2025-12-30 14:12:44,560 INFO gave up: postgresql entered FATAL state, too many start retries too quickly

Previews mounted work just fine.

I am using the docker implementation inside Unraid and the mount path is: /mnt/user/appdata/kitsu/postgres/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions