[CLI] supabase wont start

[rosmur]

Describe the bug supabase start erroring out always

To Reproduce Steps to reproduce the behavior:

1. run supabase start
2. See error:

Starting database...
Initialising schema...
Stopping containers...
error running container: exit 1

with --debug flag:

 InternalError: (e, message) => new import_storage_error.StorageBackendError({
                                 ^

StorageBackendError: Migration iceberg-catalog-ids not found
    at Object.InternalError (/app/dist/internal/errors/codes.js:248:34)
    at /app/dist/internal/database/migrations/migrate.js:425:36
    at async /app/dist/internal/database/migrations/migrate.js:553:14
    at async connectAndMigrate (/app/dist/internal/database/migrations/migrate.js:383:5)
    at async runMigrationsOnTenant (/app/dist/internal/database/migrations/migrate.js:273:3)
    at async /app/dist/scripts/migrate-call.js:30:3 {
  metadata: {},
  code: 'InternalError',
  httpStatusCode: 500,
  userStatusCode: 500,
  originalError: undefined,
  resource: undefined,
  error: undefined
}

Expected behavior Supabase starts up normally.

Crash ID:

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

• Ticket ID: [e.g. 5acbb1defe45429d854d3d1c1f2d370c]
• Version of OS: Debian 12 bookworm
• Version of CLI: 2.59.2
• Version of Docker: 28.5.1-1
• Versions of services:

SERVICE IMAGE	LOCAL	LINKED
supabase/postgres	17.6.1.048	17.6.1.048
supabase/gotrue	v2.182.1	v2.182.1
postgrest/postgrest	v13.0.5	v13.0.5
supabase/realtime	v2.63.3	-
supabase/storage-api	v1.30.0	-
supabase/edge-runtime	v1.69.24	-
supabase/studio	2025.11.10-sha-5291fe3	-
supabase/postgres-meta	v0.93.1	-
supabase/logflare	1.26.4	-
supabase/supavisor	2.7.4	-

Additional context

• Running in devcontainer: uses python:3-bookworm base image, supabase-cli feature along with docker-in-docker feature