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

General
1

Hi,

I am in a sveltekit project using supabase. There is no supabase folder that is automatically generated by running the supabase commands. I have been working on the supabase cloud for my project, but now want to generate the migrations files for all the tables, and also the SQL for all the scripts I’ve used in my project.

in the logs, I get this:

0:35:27.739068Z INFO vector: Vector has stopped.

2025-04-19T10:35:27.740391Z INFO vector::topology::running: Shutting down... Waiting on running components. remaining_components="logflare_functions, logflare_realtime, logflare_auth, logflare_db, kong_err, db_logs, logflare_rest, logflare_kong, auth_logs, realtime_logs, rest_logs, logflare_storage" time_remaining="59 seconds left"

Stopping containers...

supabase_vector_lookatmyapp-web container is not ready: unhealthy

Removing and deleting the containers doesn’t work. Have tried restarting the laptop and repeating everything too.

Running the command with --debug shows:

5/04/19 15:43:10 Recv First Byte

Stopping containers...

Pruned containers: [79c9bcdb7030451eb27320eaebb5001d254ace4ab089089356de03c33d3725e7 c930f948f88272cea9ccb1a97f8c4c37b1551f6870a95361e930aa35e5b3bdc6 09e76dbb00fe2cbad05bfeec972fc9fc3d5bf08f0c6bff34f57153379e02fe56]

Pruned volumes: [supabase_db_lookatmyapp-web supabase_config_lookatmyapp-web]

Pruned network: [supabase_network_lookatmyapp-web]

failed to create docker container: Error response from daemon: Conflict. The container name "/supabase_vector_lookatmyapp-web" is already in use by container "09e76dbb00fe2cbad05bfeec972fc9fc3d5bf08f0c6bff34f57153379e02fe56". You have to remove (or rename) that container to be able to reuse that name.

However, when I try to list the containers, this one doesn’t exist at all.

1 Like
2

got exact same issue, I tried with deleting all the images as well, but still get this error

3

And how do you list the containers? Make sure you add -a like

docker ps -a

to list stopped containers.

What is the difference between removing and deleting? Please, sho exact commands you tried. The error message seems to be clear about the already used name. If you don’t see that name even among stopped containers, then maybe the tool you are using to deploy the containers is the one that duplicates and then deletes containers and you could try a Supabase forum. I’m not familiar with it, but I found this:

https://github.com/orgs/supabase/discussions

Not sure if this is what you need..

4

I used these to view the list of containers. It didn’t bring up any container’s name.

docker ps -a --filter name=supabase_vector
docker container ls -a

I used these to remove all containers and the associated elements:

docker volume prune -f
docker network prune -f
docker system prune -af --volumes
docker container prune -f 
docker system prune -a --volumes

I used these to try to remove the particular container, but it would result in an error saying that the container doesn’t exist:

docker rm -f supabase_vector_lookatmyapp-web 
docker rm -f c8c74d166f8ea4195bf2cd442f911721c7492f1e5341262e86dc2099f939a3a2
5

Sorry about that. I meant deleting and removing to be the same.

6

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.

7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.