SupabaseS
Supabase•6mo ago
Dirx

Storage Error on `supabase start` After CLI Update

I just updated to CLI version 2.31.4 (the latest). I then cleared my supabase local volumes in docker and then ran 
supabase start
. It performs the migrations (because the volumes were cleared), and then tries do a GET to the storage API, and I get this error:

...
WARNING: analytics requires mounting default docker socket: /var/run/docker.sock
2025/07/16 11:55:14 HTTP GET: http://127.0.0.1:54321/storage/v1/bucket
Stopping containers...
Pruned containers: [...(redacted)]
Pruned volumes: [supabase_edge_runtime_dossier-sb-local supabase_db_dossier-sb-local supabase_config_dossier-sb-local supabase_storage_dossier-sb-local]
Pruned network: [supabase_network_dossier-sb-local]
Error status 500: {"statusCode":"500","code":"DatabaseError","error":"DatabaseError","message":"select * from ((select \"id\", \"name\", \"type\", \"public\", \"owner\", \"created_at\", \"updated_at\", \"file_size_limit\", \"allowed_mime_types\" from \"buckets\") union all (select \"id\", \"id\" as \"name\", \"type\", null as \"public\", null as \"owner\", \"created_at\", \"updated_at\", null as \"file_size_limit\", null as \"allowed_mime_types\" from \"buckets_analytics\")) as \"all_buckets\" - column \"type\" does not exist"}


I did a relink as well, but this did not fix the issue. Not sure what the next troubleshooting steps are, but everything was fine before the CLI update.

Thanks for the help. 🙂
Was this page helpful?