container is not healthy, no such container errors whenever project is linked

[sai-sy]

Whenever the project is linked I get errors that container is not health and no such container exists. I get that error on start db diff db pull db resetit doesn't matter. It goes away if Irm -rf supabase/.temp` which works unless I need to db diff or db pull which I am trying to do because I am trying to clean up my local dev flow

failed to read docker logs: Error response from daemon: No such container: df4152069b6c8b77c270749220cf7178a318588bb1bef034852f9f9056b27042
Failed to remove container: df4152069b6c8b77c270749220cf7178a318588bb1bef034852f9f9056b27042 Error response from daemon: No such container: df4152069b6c8b77c270749220cf7178a318588bb1bef034852f9f9056b27042
failed to inspect container health: Error response from daemon: No such container: df4152069b6c8b77c270749220cf7178a318588bb1bef034852f9f9056b27042

Just like the error I've linked, when runnign supabase db diff a container pops up for a second, then goes away. I assume thats why it gives the error "no such container". I've changed db.health_timeout'"4m" and still have the same issue. I try running it with the supabase start or supabase stop. Doesn't help. It's pretty much made fleshing out a proper dev flow impossible.

@sweatybridge Same thing happens for me, a container with the shadow database is created, but after a few seconds it is deleted.

Screen.Recording.2024-06-24.at.12.39.03.mov

Services output:

Originally posted by @jkaczmarek1 in #1894

[sai-sy]

this guy says its to do with the auth schema but running supabase db pull -s public doesn't fix it for me the way it does him