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

supabase / cli / 40670719523
47%
develop: 46%

Build:
Build:
LAST BUILD BRANCH: gh-readonly-queue/develop/pr-7380-74d4774766936b6e6141a58d061c3396a01c85c9
DEFAULT BRANCH: develop
Ran 28 Oct 2026 10:16AM 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

28 Oct 2026 10:15AM UTC coverage: 46.568%. Remained the same
40670719523

push

github

web-flow
fix(cli): start the local stack when Docker cannot exec health checks (#7362)

## Summary

On some nested or sandboxed Docker hosts, `docker start` works but
`docker exec` doesn't. runc can't join the container's namespaces, so
every exec fails with `OCI runtime exec failed: … error executing setns
process: exit status 1`. Docker runs every `HEALTHCHECK` through exec,
so on these hosts no container ever turns healthy.

`supabase start` waited on Docker health for Postgres, so it sat out the
whole `db.health_timeout` (2 minutes by default), failed with
`HealthCheckTimeoutError … container is not ready: unhealthy` and rolled
the stack back. The real reason, the setns error in `State.Health.Log`,
was never shown.

This makes the readiness checks work without Docker being able to exec
into containers, and puts the health-check output in the error when
something genuinely isn't ready.

### What changes

- Postgres readiness is a connection from the host. `start`, `db start`,
`db reset`, and the shadow databases for `db diff` and `migration
squash` now wait until Postgres accepts a connection on its published
port. It's the same probe the pg-delta shadow already used. The db gate
doesn't read Docker health any more.
- Other services fall back when their health check can't run. That means
the last health check failed to exec (exit code -1, `OCI runtime exec
failed`), and the failure isn't a missing or broken health-check command
in the image. In that case the gate checks:
- the Kong-routed services (Auth, Storage, postgres-meta, Analytics)
through their health route in Kong, which has to return 200
  - Kong itself by any HTTP response from its proxy
  - everything else by it running

`start` then prints one warning that names the containers it could only
confirm as running.
- `status` and the already-running check on `start` accept a db whose
health check can't exec, with the same warning, instead of failing.
- Not-ready errors say why. They now include the ... (continued)

5591 of 12006 relevant lines covered (46.57%)

25.05 hits per line

Jobs
ID Job ID Ran Files Coverage
1 40670719523.1 28 Oct 2026 10:16AM UTC 119
46.57
GitHub Action Run
Source Files on build 40670719523
  • 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 #40670719523
  • dbc4dfbc on github
  • Prev Build on gh-readonly-queue/develop/pr-7334-2aa018f4cb0c948cc4968038a6b2c98a242f1f73 (#40668262416)
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