• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

supabase / cli / 40873968264
47%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 29 Oct 2026 12:32PM UTC
Jobs 1
Files 119
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

29 Oct 2026 12:31PM UTC coverage: 46.568%. Remained the same
40873968264

push

github

web-flow
fix(cli): recover start and db start from a stopped database container (#7369)

## Summary

If a `supabase start` dies after Docker creates the database container
but before it starts it, the container is left in Docker's `created`
state. That can happen if the process is killed, a port is already
taken, or a second `start` rolls back the first one's containers. Every
`supabase start` after that printed `supabase start is already running.`
and then failed with `container is not running: created`. The way out
was to remove the container by hand, and nothing pointed you there.

Looking into it turned up three more problems along the same path:

- The leftover volume never gets set up. `start` decided whether to run
the first-run setup (schema, roles, migrations, seed) purely on whether
the database volume already existed. A leftover volume that Postgres
never initialised still exists, so after `supabase stop` and `supabase
start` the setup was skipped and the stack came up without
`supabase_migrations` or any of the project's migrations.
- Two starts on one project break each other. When one fails, its
rollback prunes the project's containers and network by label, including
the ones the other start is still bringing up. Usually both fail, and
they can leave behind exactly the `created` container above.
- `db start` only checked that the database container existed. For a
stopped or never-started one it printed `Postgres database is already
running.` and exited 0 with Postgres down. The local database auto-start
in `db schema declarative generate` and `sync` used the same check,
skipped the start and then failed to connect.

This fixes all of them.

### What changes

- `start` recovers a `created` database container the same way it
already recovers an `exited` one. It removes the project's containers
and network, keeps the volumes, and brings the stack up again.
- A database container that isn't running and can't be recovered (an
unknown state, or Bitbuck... (continued)

5591 of 12006 relevant lines covered (46.57%)

25.09 hits per line

Jobs
ID Job ID Ran Files Coverage
1 40873968264.1 29 Oct 2026 12:32PM UTC 119
46.57
GitHub Action Run
Source Files on build 40873968264
  • Tree
  • List 119
  • Changed 0
  • Source Changed 0
  • Coverage Changed 0
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #40873968264
  • fd2e017d on github
  • Prev Build on gh-readonly-queue/develop/pr-7390-097b7f2bd330bb99b4b8ea49efd1f5953b5edb02 (#40869302139)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc