2
`supase start --exclude <container>` shouldn't pull the image for `<container>`
Source: supabase/supabase#12576 · opened by @joeally
Currently supabase start always pulls all of the images that aren't present even if exclusion flags are supplied. Ideally only the containers that are needed should be pulled.
This is obviously not a dealbreaker but it does needlessly slow down my CI job significantly as it spends a lot of time pulling docker images it never uses.
This is obviously not a dealbreaker but it does needlessly slow down my CI job significantly as it spends a lot of time pulling docker images it never uses.
No pledges yet. Be the first to back this.
Comments
Similar requests
Add `include` option for `supabase start`
3 votes · 0 comments
Adhere to excludedSchemas List to Limit Functions Returned
1 vote · 0 comments
supabase pause command for cli
1 vote · 0 comments
Add `supabase config pull` command
62 votes · 0 comments
Work with OpenAI to provide a Codex-optimized Supabase image or runtime for agent-based development
7 votes · 0 comments
No comments yet.