© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•6mo ago•
2 replies
peaches

postgres missing exposed ports

I run the stack locally for testing via the supabase cli. When looking at the docker containers, the postgres one is expected to have its internal port exposed externally on 54322 however its not showing

a) The docher run command is correct:
-p 54322:5432
b) Supabase status shows the expected postgresql://postgres:postgres@127.0.0.1:54322/postgres
c) netstat -an missing the port LISTEN mode
d) Same thing in docker desktop the port is not opened I cannot reach it (see docker desktop screenshot)

supabase cli version
pnpm supabase --version
2.34.3

$ pnpm supabase status
Stopped services: [supabase_imgproxy_supabase supabase_pooler_supabase]
supabase local development setup is running.

API URL: http://127.0.0.1:54321
GraphQL URL: http://127.0.0.1:54321/graphql/v1
S3 Storage URL: http://127.0.0.1:54321/storage/v1/s3
DB URL: postgresql://postgres:postgres@127.0.0.1:54322/postgres
Studio URL: http://127.0.0.1:54323
Inbucket URL: http://127.0.0.1:54324


I'm running it inside WSL on windows and my docker is windows based. That used to work until I updated to the latest cli version.
Screenshot_2025-08-15_173514.png
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources

Similar Threads

Was this page helpful?
Recent Announcements

Similar Threads

supabase/postgres container missing
SupabaseSSupabase / help-and-questions
14mo ago
Postgres grant / revoke queries missing in diff
SupabaseSSupabase / help-and-questions
3y ago
STORAGE SCHEMA NOT EXPOSED
SupabaseSSupabase / help-and-questions
2mo ago
query exposed on client side
SupabaseSSupabase / help-and-questions
12mo ago