On running supabase start, "supabase_vector_lookatmyapp-web container is not ready: unhealthy" appears

Then I still think it is the supabase command that duplicates containers. We had similar issues related to supabase before:

The above issue was about ports, but I suspected the same, duplicating containers. You can also find issues about naming like this:

But youf first error message in your first post was the process stopping in the container, so normally it would work, but then the debug mode breaks it. You really need someone who uses supabase. as it seems to be an application issue so far.