Supabase containers automagically restart after having been manually stopped

[adamcameron]

Describe the bug
I'm not sure this is a bug. It's bloody annoying though.

Right so running supabase cli on my local machine. When I run supabase start, it creates and starts a dozen or so containers. All works fine. Nice one.

Now, normal Docker usage in dev would be "OK, don't need these services running ATM, so press STOP in docker desktop. And the containers... stop".

I'm pretty sure this used to work on the Supabase containers too. However today I stopped them and.... they just started again. Seriously Supabase: "stop means stop", we all know that these days.

I realise I can go npx superbase stop, but that also blows the containers away. I don't wanna do that, I just want them to stop. By pressing the "stop" button. There's a hint in that somewhere I think. I can't quite see it.

I am running 2.65.6 (this downloaded this morning).

I get that having "restart unless stopped" as a restart policy: that makes sense. But not "nono, I'm just always gonna restart cos I know better than the human pushing the stop button".

To Reproduce

See above.

Expected behavior

See above.

Screenshots

N/A

System information

• Version of OS: 24.04.2 LTS (via WSL on Win11)

• Version of CLI: 2.65.6

• Version of Docker: 4.52.0

• Versions of services:

  SERVICE IMAGE | LOCAL | LINKED
  ------------------------|------------------------|--------
  supabase/postgres | 17.6.1.059 | -
  supabase/gotrue | v2.183.0 | -
  postgrest/postgrest | v14.1 | -
  supabase/realtime | v2.67.2 | -
  supabase/storage-api | v1.32.1 | -
  supabase/edge-runtime | v1.69.28 | -
  supabase/studio | 2025.12.01-sha-4ad48b7 | -
  supabase/postgres-meta | v0.93.1 | -
  supabase/logflare | 1.26.20 | -
  supabase/supavisor | 2.7.4 | -

Additional context

N/A

"Thank you for your attention to this matter!" as goes the zeitgeist these days...

[silentworks]

npx supabase stop does not blow the container away as the volume where it stores the states are maintained unless you add the --no-backup flag. Docker will restart some containers depending on how they were started when you try and stop them from docker desktop. The documented way to stop a Supabase container is as you stated (npx supabase stop) and that is the best way to go.