StorageBackendError: Migration iceberg-catalog-ids not found
Bug report
- [x] I confirm this is a bug with Supabase, not with my own application.
- [x] I confirm I have searched the Docs, GitHub Discussions, and Discord.
Describe the bug
Self-hosted Supabase fails to start because the storage-api container crashes during its internal migrations with: Migration iceberg-catalog-ids not found (StorageBackendError, status 500). As a result supabase start stops all containers and the stack never becomes healthy.
To Reproduce
-
Clean environment: docker system prune -a --volumes (so no cached images/volumes remain).
-
In a Supabase project directory (with supabase/config.toml etc.), run supabase start --debug (CLI 2.58.5).
-
Images pull successfully. Postgres and Realtime initialize.
-
When public.ecr.aws/supabase/storage-api:v1.29.0 starts, it crashes with:
StorageBackendError: Migration iceberg-catalog-ids not found at /app/dist/internal/database/migrations/migrate.js:425:36
-
CLI stops all services and exits.
Expected behavior
Local supabase start should bring up all services, including storage-api, without missing internal migrations.
Screenshots
System information
- OS: Ubuntu 22.04 (x86_64, Docker)
- Browser: N/A (CLI)
- Supabase CLI: 2.58.5
- Node.js (inside storage-api): 22.21.1 (from container log)
- Storage image: public.ecr.aws/supabase/storage-api:v1.29.0 (also reproduced with fresh pull after prune)
- Docker: 27.1.x
Additional context
-
Happens on a clean machine with no prior Supabase volumes or images.
-
Postgres, Realtime, etc. start fine; only storage-api fails its own migration step.
-
Previous storage-api tags (e.g., v1.27.6) reportedly worked; current latest fails consistently.
-
Full log snippet:
/app/dist/internal/errors/codes.js:242 StorageBackendError: Migration iceberg-catalog-ids not found at /app/dist/internal/database/migrations/migrate.js:425:36 at async connectAndMigrate ...
Hello,
I want to add that this also happen on remote project and with
npx supabase db pull
And is a critical error
Ran into same issue with supabase start
running pnpx supabase start resolved the issue
verified the latest cli is installed via brew
This should now be resolved with latest cli please let me know if it's not the case