© 2026 Hedgehog Software, LLC

TwitterGitHubDiscord
More
CommunitiesDocsAboutTermsPrivacy
Search
Star
Setup for Free
SupabaseS
Supabase•3mo ago•
32 replies
vick

Error "Migration iceberg-catalog-ids not found" after supabase link

CLI
I upgraded my cloud DB today which brought in postgres 17.6.1.048. After linking to my dev instance via the CLI (version 2.58.5 which npm says is the latest), the DB refuses to start, offering the following error repeatedly:

{"level":50,"time":"2025-11-17T15:34:12.015Z","pid":1,"hostname":"56eec84e81c7","region":"not-specified","type":"startupError","error":{"raw":"{\"metadata\":{},\"code\":\"InternalError\",\"httpStatusCode\":500,\"userStatusCode\":500}","name":"Error","message":"Migration iceberg-catalog-ids not found","stack":"Error: Migration iceberg-catalog-ids not found\n    at Object.InternalError (/app/dist/internal/errors/codes.js:242:34)\n    at /app/dist/internal/database/migrations/migrate.js:425:36\n    at async /app/dist/internal/database/migrations/migrate.js:553:14\n    at async connectAndMigrate (/app/dist/internal/database/migrations/migrate.js:383:5)\n    at async runMigrationsOnTenant (/app/dist/internal/database/migrations/migrate.js:273:3)\n    at async main (/app/dist/start/server.js:68:5)","statusCode":500},"msg":"Server not started with error"}
{"level":50,"time":"2025-11-17T15:34:12.015Z","pid":1,"hostname":"56eec84e81c7","region":"not-specified","type":"startupError","error":{"raw":"{\"metadata\":{},\"code\":\"InternalError\",\"httpStatusCode\":500,\"userStatusCode\":500}","name":"Error","message":"Migration iceberg-catalog-ids not found","stack":"Error: Migration iceberg-catalog-ids not found\n    at Object.InternalError (/app/dist/internal/errors/codes.js:242:34)\n    at /app/dist/internal/database/migrations/migrate.js:425:36\n    at async /app/dist/internal/database/migrations/migrate.js:553:14\n    at async connectAndMigrate (/app/dist/internal/database/migrations/migrate.js:383:5)\n    at async runMigrationsOnTenant (/app/dist/internal/database/migrations/migrate.js:273:3)\n    at async main (/app/dist/start/server.js:68:5)","statusCode":500},"msg":"Server not started with error"}


Digging a bit, I found in the
supabase/.temp
supabase/.temp
folder a file called
storage-migration
storage-migration
with the value
iceberg-catalog-ids
iceberg-catalog-ids
. Removing that file allows the DB to start.

Further, I see that the file
storage-version
storage-version
has
v1.31.1
v1.31.1
but the docker image for that is never fetched. The cli is still running storage image v1.29.0. My hunch is that 1.29.0 does not have the necessary bits to run this "iceberg" migration.

Why would the cli ignore the storage version specified?
Supabase banner
SupabaseJoin
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
45,816Members
Resources
Was this page helpful?

Similar Threads

Recent Announcements

Similar Threads

Using Iceberg with Supabase
SupabaseSSupabase / help-and-questions
8mo ago
Supabase Migration Error
SupabaseSSupabase / help-and-questions
4mo ago
supabase link
SupabaseSSupabase / help-and-questions
2mo ago
Supabase migration confusion
SupabaseSSupabase / help-and-questions
6mo ago