Open sweigert opened 3 days ago
Could this be related to https://github.com/supabase/postgres/pull/1125? Would also coincide with the incident in the supabase cloud and does exactly change what fails for me now.
Maybe I'm using it all wrong and I'm supposed to do it differently but I'm not sure how.
Update: I got it working by not specifying a custom database and by either using supabase_admin
as the POSTGRES_USER
or not specifying this env var at all (since this seems to be the default now anyway).
It seems all the user role wrangling that is done here does not do all the work if I pass a custom DB.
This could turn out really bad for people who host supabase themselves and use custom databases (i.e., not postgres
).
This is working now:
docker run --rm \
--name test-db \
-e POSTGRES_PASSWORD=postgres \
-p 5432:5432 \
public.ecr.aws/supabase/postgres:15.6.1.120
Bug report
Describe the bug
I used to be able to run a local supabase/postgres using the postgres user and setting a password. This is helpful for running backend tests against an actual supabase instance.
However, since supabase/postgres:15.6.1.120 this does not work anymore and fails with the following error:
The same works just fine using supabase/postgres:15.6.1.119
While I can get supabase/postgres:15.6.1.120 to start just fine using
-e POSTGRES_USER=supabase_admin
this does not work for me as the postgres user then has no right to write to the public schema inmy-backend
and I am not able to login with the supabase_adminTo Reproduce
This fails to start:
This runs just fine:
Expected behavior
I would expect the container to start without errors and be able to write to the public schema of
my-backend
using the postgres userScreenshots
If applicable, add screenshots to help explain your problem.
System information
Additional context
I used to have a similar issue in the supabase cloud recently which led to this incident (https://status.supabase.com/incidents/5b1z81cjm3lt). This happened when I upgraded from .119 to .121 and while I obviously do not run docker in the supabase cloud I had a similar problem, not being able to connect to supabase using psql since it could not authenticate with supabase_admin.