containers will not start from CLI database `_supabase` does not exist
1. downloaded a new version of the CLI
2. run supabase start -> downloads new versions of the images (not sure thats related at all to CLI update)
compose fails to launch all dockers
`
2. run supabase start -> downloads new versions of the images (not sure thats related at all to CLI update)
compose fails to launch all dockers
WARN: no seed files matched pattern: supabase/seed.sql
WARN: no SMS provider is enabled. Disabling phone login
WARNING: You are running different service versions locally than your linked project:
supabase/storage-api:v1.11.0 => v1.14.4
supabase/gotrue:v2.160.0 => v2.168.0
Run supabase link to update them.
WARNING: analytics requires mounting default docker socket: /var/run/docker.sock
supabase_analytics_supabase container logs:
17:37:06.195 [error] Postgrex.Protocol (#PID<0.161.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:06.195 [error] Postgrex.Protocol (#PID<0.162.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:07.627 [error] Postgrex.Protocol (#PID<0.162.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:08.786 [error] Postgrex.Protocol (#PID<0.161.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:11.285 [error] Postgrex.Protocol (#PID<0.162.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:12.835 [error] Postgrex.Protocol (#PID<0.161.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:17.054 [error] Could not create schema migrations table. This error usually happens due to the following:WARN: no seed files matched pattern: supabase/seed.sql
WARN: no SMS provider is enabled. Disabling phone login
WARNING: You are running different service versions locally than your linked project:
supabase/storage-api:v1.11.0 => v1.14.4
supabase/gotrue:v2.160.0 => v2.168.0
Run supabase link to update them.
WARNING: analytics requires mounting default docker socket: /var/run/docker.sock
supabase_analytics_supabase container logs:
17:37:06.195 [error] Postgrex.Protocol (#PID<0.161.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:06.195 [error] Postgrex.Protocol (#PID<0.162.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:07.627 [error] Postgrex.Protocol (#PID<0.162.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:08.786 [error] Postgrex.Protocol (#PID<0.161.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:11.285 [error] Postgrex.Protocol (#PID<0.162.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:12.835 [error] Postgrex.Protocol (#PID<0.161.0>) failed to connect: ** (Postgrex.Error) FATAL 3D000 (invalid_catalog_name) database "_supabase" does not exist
17:37:17.054 [error] Could not create schema migrations table. This error usually happens due to the following:
