30264132566
65%
develop: 65%

Ran 27 Jul 2026 12:02PM UTC

Jobs 1

Files 230

Run time 1min

Badge

Embed ▾

Committed 27 Jul 2026 12:00PM UTC coverage: 65.289%. Remained the same

Build # 30264132566

Build Type

push

github

Committed by

web-flow

Commit Message

fix(cli): recover stopped local stack (#5953)

## TL;DR
`supabase start` now recovers a stopped local stack instead of reporting
it as already running.

## Prob
After a `Docker Desktop` restart, the local containers come back exited
instead of running.
`start` only checked that the Postgres container existed, not whether it
was actually running,
so it printed "already running" and then failed the health check with
"container is not running: exited".

we offered no way past this, users had to workaround it by hand with raw
docker commands or repeat the whole cycle...

## Sol
When Postgres is confirmed stopped, `start` removes the project's
containers and unused networks (never volumes), then reruns the normal
startup flow.

## ref
- closes #5917
- extends #5847

Coverage Stats

11250 of 17231 relevant lines covered (65.29%)

10.51 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
1	30264132566.1	27 Jul 2026 12:02PM UTC	230	65.29	GitHub Action Run

supabase / cli / 30264132566
65%
develop: 65%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 30264132566

supabase / cli / 30264132566 65% develop: 65%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 30264132566

supabase / cli / 30264132566
65%
develop: 65%

README BADGES
x