ERROR 3F000 (invalid_schema_name) no schema has been selected to create in ...

[itinance]

Describe the bug

Starting supabase from a backup, which has been downloaded from the official cloud service, gives the following error:

error running container: exit 1

Adding the --debug-switch provides more information:

Supabase CLI 2.23.4
Starting database...
+ ulimit -n
+ '[' '!' -z '' ']'
+ export ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ ERL_CRASH_DUMP=/tmp/erl_crash.dump
+ '[' false = true ']'
+ echo 'Running migrations'
+ sudo -E -u nobody /app/bin/migrate
** (Postgrex.Error) ERROR 3F000 (invalid_schema_name) no schema has been selected to create in
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1054: Ecto.Adapters.SQL.raise_sql_call_error/1
    (elixir 1.17.3) lib/enum.ex:1703: Enum."-map/2-lists^map/1-1-"/2
    (ecto_sql 3.11.3) lib/ecto/adapters/sql.ex:1161: Ecto.Adapters.SQL.execute_ddl/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:755: Ecto.Migrator.verbose_schema_migration/3
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:563: Ecto.Migrator.lock_for_migrations/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:432: Ecto.Migrator.run/4
    (ecto_sql 3.11.3) lib/ecto/migrator.ex:170: Ecto.Migrator.with_repo/3
    nofile:1: (file)
Stopping containers...
Pruned containers: [56a8ac307fe619b848a8b08a82bc71b18ddf766416e2b5f1664b2d8639e32b02]
Pruned volumes: [supabase_db_xxx-backend supabase_config_xxxx-backend]
Pruned network: [supabase_network_xxxx-backend]
error running container: exit 1

I even pruned all containers and started again, it produces the same errors.

supbase version: 2.23.4

To Reproduce
Steps to reproduce the behavior:

1. download latest backup from supabase cloud
2. supabase db start --debug --from-backup ../db_cluster-29-05-2025@00-04-18.backup

Expected behavior

it would just start and provide a database from the backup.

System information
Rerun the failing command with --create-ticket flag.

• crash report: eb67fdb2bf7f43c783b10ae3c438093d
• Version of OS: MacOS Sonoma 14.7.2 (23H311)
• Version of CLI: 2.23.4
• Version of Docker: 28.1.1, build 4eba377
• Versions of services: [output from supabase services command]
  SERVICE IMAGE | LOCAL | LINKED
  ------------------------|------------------------|------------
  supabase/postgres | 15.8.1.054 | 15.8.1.054
  supabase/gotrue | v2.170.0 | v2.173.0
  postgrest/postgrest | v12.2.3 | v12.2.3
  supabase/realtime | v2.35.3 | -
  supabase/storage-api | v1.22.17 | -
  supabase/edge-runtime | v1.67.4 | -
  supabase/studio | 2025.05.19-sha-3487831 | -
  supabase/postgres-meta | v0.89.0 | -
  supabase/logflare | 1.12.0 | -
  supabase/supavisor | 2.5.1 | -

Additional context
If applicable, add any other context about the problem here.

• Version of supabase-js 2.23
• Version of Node.js 20.17.0

[itinance]

this config settings puts the error away:

[realtime]
enabled = false