Local Supabase instance broken after CLI upgrade
CLI
SolvedHi guys,
I have upgraded the supabase cli version on my dev macbook to 2.72.7 and after restart, it pulled new versions of containers, but the very first start ended up with error:
Starting database from backup...
Starting containers...
Stopping containers...
Failed to start Docker container: Error response from daemon: error while creating mount source path '/Users/.../supabase/snippets': chown /Users/.../supabase/snippets: operation not permitted
Then on the second and subsequent runs, I'm getting an error in the storage container:
Waiting for health checks...
supabase_storage_horses container logs:
{"level":50,"time":"2026-01-20T04:55:21.329Z","pid":1,"hostname":"afb0900e224b","region":"not-specified","type":"startupError","error":{"raw":"{"cause":"error: duplicate key value violates unique constraint \"migrations_name_key\""}","name":"Error","message":"Migration failed. Reason: duplicate key value violates unique constraint "migrations_name_key"","stack":"Error: Migration failed. Reason: duplicate key value violates unique constraint "migrations_name_key"\n at /app/dist/internal/database/migrations/migrate.js:504:21\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async /app/dist/internal/database/migrations/migrate.js:578:14\n at async connectAndMigrate (/app/dist/internal/database/migrations/migrate.js:389:5)\n at async runMigrationsOnTenant (/app/dist/internal/database/migrations/migrate.js:276:3)\n at async main (/app/dist/start/server.js:94:5)","statusCode":0},"msg":"Server not started with error"}
And the whole instance doesn't start. From what I can see, the error is related to the unique constraint on the "storage.migrations" table (looks like it tries to reapply the same migration again).
Would be very grateful for directions!
Thanks
Tom
I have upgraded the supabase cli version on my dev macbook to 2.72.7 and after restart, it pulled new versions of containers, but the very first start ended up with error:
Starting database from backup...
Starting containers...
Stopping containers...
Failed to start Docker container: Error response from daemon: error while creating mount source path '/Users/.../supabase/snippets': chown /Users/.../supabase/snippets: operation not permitted
Then on the second and subsequent runs, I'm getting an error in the storage container:
Waiting for health checks...
supabase_storage_horses container logs:
{"level":50,"time":"2026-01-20T04:55:21.329Z","pid":1,"hostname":"afb0900e224b","region":"not-specified","type":"startupError","error":{"raw":"{"cause":"error: duplicate key value violates unique constraint \"migrations_name_key\""}","name":"Error","message":"Migration failed. Reason: duplicate key value violates unique constraint "migrations_name_key"","stack":"Error: Migration failed. Reason: duplicate key value violates unique constraint "migrations_name_key"\n at /app/dist/internal/database/migrations/migrate.js:504:21\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async /app/dist/internal/database/migrations/migrate.js:578:14\n at async connectAndMigrate (/app/dist/internal/database/migrations/migrate.js:389:5)\n at async runMigrationsOnTenant (/app/dist/internal/database/migrations/migrate.js:276:3)\n at async main (/app/dist/start/server.js:94:5)","statusCode":0},"msg":"Server not started with error"}
And the whole instance doesn't start. From what I can see, the error is related to the unique constraint on the "storage.migrations" table (looks like it tries to reapply the same migration again).
Would be very grateful for directions!
Thanks
Tom
