vector container fails with "exec format error" on Apple M2

[ta1yo1022]

Describe the bug

When running supabase start on an Apple M2 chip (macOS), the supabase_vector_library-backend container fails to start with an exec format error. This occurs even when the vector service is explicitly disabled in config.toml.

Environment

Software | Version -- | -- OS | macOS (Apple M2 chip) Supabase CLI | 2.70.5 Docker Desktop | 29.1.3 Node.js | v25.1.0

To Reproduce

1. Initialize a Supabase project: npx supabase init

2. Configure supabase/config.toml to disable vector storage:

   [storage.vector]
   enabled = false
   

3. Run npx supabase start

4. Observe the logs for the vector container.

Expected behavior

• The CLI should pull the ARM64 compatible image for the vector service on Apple Silicon.

• Alternatively, if [storage.vector] enabled = false is set, the CLI should not attempt to pull or start the vector container at all.

Actual behavior

The CLI attempts to start the vector container, which fails with the following logs:

supabase_vector_library-backend container logs:
exec /bin/sh: exec format error
exec /bin/sh: exec format error
...
Stopping containers...
supabase_vector_library-backend container is not ready: unhealthy

Additional context

• I have tried npx supabase stop, removing all containers/volumes, and docker system prune -a, but the issue persists.

• The exec format error suggest that an x86_64 image is being pulled instead of an ARM64 one, or the entrypoint script is incompatible.

• It seems the enabled = false flag in config.toml is being ignored for this specific service.

[singh-inder]

The error you're seeing is from vector container. Not sure about the img pull error but to disable it you need to set analytics.enabled = false

You can also pass the service to disable via a flag:

npx supabase start -x vector,logflare

cc @aantti

[aantti]

Curious what does docker image inspect public.ecr.aws/supabase/vector:0.28.1-alpine --format '{{.Architecture}}' say, @ta1yo1022