cli
cli copied to clipboard
supabase
supabase start (v1.167.4) crashes
Describe the bug supbase start fails
To Reproduce Steps to reproduce the behavior:
- Install supabase cli via yarn:
yarn add supabase --group dev - Run
yarn supabase init - Run
yarn supabase start - See error
❯ yarn supabase db start --create-ticket
yarn run v1.22.22
warning package.json: No license field
$ /home/luis/Code/tttt/project/node_modules/.bin/supabase db start --create-ticket
Starting database...
15.1.1.41: Pulling from supabase/postgres
17d0386c2fff: Pull complete
ec8061954605: Pull complete
e54d94900333: Pull complete
3be4d2664419: Pull complete
5d3911bdcee3: Pull complete
33719a05f4ef: Pull complete
cd5341e6fcf9: Pull complete
083e9066a8a9: Pull complete
15e57519e2e1: Pull complete
c5573b8f6e79: Pull complete
8e4d4e9e7ffa: Pull complete
7819f3b4135b: Pull complete
bfb56fc535a5: Pull complete
8745eb852041: Pull complete
90bb658328ea: Pull complete
883d9b8ba5fc: Pull complete
de3891c7e975: Pull complete
4d1c60b79844: Pull complete
bc35e3236cd4: Pull complete
247f832137f9: Pull complete
f8853832fdf5: Pull complete
6e9addf2cb83: Pull complete
fcd0db09bbd6: Pull complete
8e2074a64d8c: Pull complete
Digest: sha256:b954155da45d6ac4cde6c9b681e9b4867eedec4c7b6944aca99828d7d8add095
Status: Downloaded newer image for public.ecr.aws/supabase/postgres:15.1.1.41
Setting up initial schema...
v2.28.32: Pulling from supabase/realtime
3f9582a2cbe7: Pull complete
ead1aa3d6db7: Pull complete
193102f091d2: Pull complete
da790444238d: Pull complete
f24e8300a30f: Pull complete
63d268445a3d: Pull complete
431c10b0c0ef: Pull complete
4a4b9749f816: Pull complete
85c6cbdc9664: Pull complete
dc630cfa1cb3: Pull complete
b76a9a75fe56: Pull complete
a47fab168e2c: Pull complete
Digest: sha256:76fb18ed93da52e3eaf63836516eaee4543abff91386a0380543ad6734e90e54
Status: Downloaded newer image for public.ecr.aws/supabase/realtime:v2.28.32
error running container: exit 1
Try rerunning the command with --debug to troubleshoot the error.
Sent crash report: f0d1f748108c4cde8a6b9cbd616c4085
Quote the crash ID above when filing a bug report: https://github.com/supabase/cli/issues/new/choose
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
System information
Rerun the failing command with --create-ticket flag.
- Ticket ID: f0d1f748108c4cde8a6b9cbd616c4085
- Version of OS: Ubuntu 22.04
- Version of CLI: 1.167.4
- Version of Docker: 26.1.2
- Versions of services:
SERVICE IMAGE │ LOCAL │ LINKED
─────────────────────────┼──────────────────────┼─────────
supabase/postgres │ 15.1.1.41 │ -
supabase/gotrue │ v2.149.0 │ -
postgrest/postgrest │ v12.0.1 │ -
supabase/realtime │ v2.28.32 │ -
supabase/storage-api │ v1.0.6 │ -
supabase/edge-runtime │ v1.49.0 │ -
supabase/studio │ 20240506-2976cd6 │ -
supabase/postgres-meta │ v0.80.0 │ -
supabase/logflare │ 1.4.0 │ -
bitnami/pgbouncer │ 1.20.1-debian-11-r39 │ -
darthsim/imgproxy │ v3.8.0 │ -
Additional context If applicable, add any other context about the problem here.
- Browser: N/A
- Version of supabase-js: 1.167.4
- Version of Node.js: v20.13.1
- Version of Yarn: 1.22.22
Using v1.164 as a workaround:
docker system prune --all --force
yarn add [email protected] --group dev
yarn supabase start
...
Started supabase local development setup.
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:[email protected]:54322/postgres
Studio URL: http://127.0.0.1:54323
Inbucket URL: http://127.0.0.1:54324
JWT secret: super-secret-jwt-token-with-at-least-32-characters-long
anon key: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6ImFub24iLCJleHAiOjE5ODM4MTI5OTZ9.CRXP1A7WOeoJeXxjNni43kdQwgnWNReilDMblYTn_I0
service_role key: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZS1kZW1vIiwicm9sZSI6InNlcnZpY2Vfcm9sZSIsImV4cCI6MTk4MzgxMjk5Nn0.EGIM96RAZx35lJzdJsyH-qQwv8Hdp7fsn3W0YpN81IU
S3 Access Key: 625729a08b95bf1b7ff351a663f3a23c
S3 Secret Key: 850181e4652dd023b7a98c58ae0d2d34bd487ee0cc3254aed6eda37307425907
S3 Region: local
Done in 160.40s.
Not sure if this is still an issue in v1.172.2 so feel free to reopen if it is still not working.
