You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-02-15T13:24:08.564341000Z
2025-02-15T13:24:08.579532000Z 2025-02-15 13:24:08.579 UTC [1] LOG: pgaudit extension initialized
2025-02-15T13:24:08.586067000Z 2025-02-15 13:24:08.585 UTC [1] LOG: pgsodium primary server secret key loaded
2025-02-15T13:24:08.586589000Z 2025-02-15 13:24:08.586 UTC [1] FATAL: The getkey script "/usr/share/postgresql/extension/pgsodium_getkey" does not exist.
2025-02-15T13:24:08.586620000Z 2025-02-15 13:24:08.586 UTC [1] DETAIL: The getkey script fetches the primary server secret key.
2025-02-15T13:24:08.586641000Z 2025-02-15 13:24:08.586 UTC [1] HINT: You might want to create it and/or set "vault.getkey_script" to the correct path.
2025-02-15T13:24:08.586668000Z 2025-02-15 13:24:08.586 UTC [1] LOG: database system is shut down
can be reproduced with
17.0.1.035-orioledb
15.8.1.039
I confirm this is a bug with Supabase, not with my own application.
FATAL: The getkey script "/usr/share/postgresql/extension/pgsodium_getkey" does not exist.
Console output:
can be reproduced with
Describe the bug
The docker container does not start. The container does start with version 15.8.1.034
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
docker compose up -d supabase-db
Expected behavior
when I initially start a container it is healthy
System information
The text was updated successfully, but these errors were encountered: