Supabase start giving "failed to display json stream" error

[SeonaidhMorrison]

Describe the bug When I try to run supabase start using supabase cli locally, I am met with this error: failed to display json stream: failed to extract layer sha256:{shakey}: failed to get reader from content store: blob sha256:{shakey} expected at /var/lib/desktop-containerd/daemon/io.containerd.content.v1.content/blobs/sha256/{shakey}: blob not found: not found

To Reproduce Steps to reproduce the behavior:

1. Run supabase init successfully
2. Set up docker on device
3. Try to run supabase start as admin

Expected behavior Supabase start works as expected

Screenshots If applicable, add screenshots to help explain your problem.

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

• Ticket ID: [611f3a9cf1584f5c9fc3bcb2b7df0664]
• Version of OS: [Windows 11]
• Version of CLI: [v1.169.6]
• Version of Docker: [4.30.0]
• Version of Services SERVICE IMAGE │ LOCAL │ LINKED ─────────────────────────┼──────────────────────┼──────────── supabase/postgres │ 15.1.1.25 │ 15.1.1.25 supabase/gotrue │ v2.151.0 │ v2.151.0 postgrest/postgrest │ v12.0.2 │ v12.0.2 supabase/realtime │ v2.28.32 │ - supabase/storage-api │ v1.2.1 │ v1.2.1 supabase/edge-runtime │ v1.53.3 │ - supabase/studio │ 20240514-6f5cabd │ - supabase/postgres-meta │ v0.80.0 │ - supabase/logflare │ 1.4.0 │ - bitnami/pgbouncer │ 1.20.1-debian-11-r39 │ - darthsim/imgproxy │ v3.8.0 │ -

[sweatybridge]

Could you check that Use containerd ... option is unset in docker settings?

This might be caused by api differences between docker engine and containerd.

[SeonaidhMorrison]

Could you check that Use containerd ... option is unset in docker settings?

This might be caused by api differences between docker engine and containerd.

This worked! Thanks for your help