feat(cli): add SUPABASE_USE_SLIM_IMAGES flag for slim ghcr images - #6382
Open
avallete wants to merge 7 commits into
Open
feat(cli): add SUPABASE_USE_SLIM_IMAGES flag for slim ghcr images#6382avallete wants to merge 7 commits into
avallete wants to merge 7 commits into
Conversation
When SUPABASE_USE_SLIM_IMAGES is true or 1, the legacy shell resolves local-stack Docker images from the slim ghcr.io/supabase/cli/ builds instead of the docker.io images pinned in the embedded Dockerfile. Services with no slim build stay on docker.io. With the flag unset, behavior is unchanged. Co-authored-by: Cursor <cursoragent@cursor.com>
Published slim images now match docker.io for the services those comments described, so they no longer claim missing migrate-call.js, a distroless-only shell pin, or a slim-baked transform default. Co-authored-by: Cursor <cursoragent@cursor.com>
avallete
changed the title
This was referenced Aug 28, 2026
Contributor
Supabase CLI previewnpx --yes https://pkg.pr.new/supabase/cli/supabase@5db428081cbfcddb992e4bbf67c4fccd566cfaafPreview package for commit |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 17f9ef48fc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
The stack catalog maps those services to ghcr.io/supabase/{supavisor,vector},
so the flag pulled the wrong images and skipped the slim runtime forks.
Keep catalog tag normalization, then always emit ghcr.io/supabase/cli/<service>.
Co-authored-by: Cursor <cursoragent@cursor.com>
The flag-off match case hardcoded postgres 17.6.1.165 after the pin moved to 17.6.1.166, so the test was committed red. Co-authored-by: Cursor <cursoragent@cursor.com>
Slim Vector ships sh and wget, so both families share the heredoc entrypoint. Drop leftover tests that only restated the shared docker.io spec. Co-authored-by: Cursor <cursoragent@cursor.com>
![depthfirst-app[bot]](https://avatars.githubusercontent.com/in/1021002?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 86ba7c4c66
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Auth, studio, and pg-meta now share docker.io healthchecks after the latest slim images. Elixir probes stay on PATH wget; analytics keeps the image entrypoint because the binary lives at /app/bin/logflare. Co-authored-by: Cursor <cursoragent@cursor.com>
…moval Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds an opt-in ambient env flag
SUPABASE_USE_SLIM_IMAGES(trueor1) that rewrites local-stack Docker image names from the embedded Dockerfile pins to the slimghcr.io/supabase/cli/<service>builds.Published slim postgres/storage/auth/edge-runtime images now match the docker.io contracts (root start,
sh/wget), so the flag is an image-name rewrite rather than a second runtime. Spec builders still branch for services that remain distroless (auth/studio/pg-meta healthchecks, pooler/realtime/analytics busybox wget, VectorsecretFiles). Kong, thediffer/migra/pgprovejob images, pg 13/14/15 fallbacks, OrioleDB, anddeno_version = 1stay on docker.io. Slim refs skipSUPABASE_INTERNAL_IMAGE_REGISTRY. With the flag unset, behavior is unchanged.The rewrite always targets
ghcr.io/supabase/cli/<service>. The stack catalog's vector/pooler mirrors (ghcr.io/supabase/{vector,supavisor}) are not used.This is the code layer of a stack that splits the previous mixed review on #6329. Docs live in #6383.
Linked issue
Closes #
open-for-contributionlabel (or I'm a Supabase maintainer).Checklist
fix(cli): …).pnpm check:allpasses; relevant package tests pass for every touched workspace, andpnpm types:checkpasses for each touched TypeScript workspace (or workspace declaring it).