Feature Request: Support Authenticated Image Registries (e.g. Dependency Proxy)

[ffabss]

Is your feature request related to a problem? Please describe.
The Supabase CLI allows configuring a custom image registry for pulling Supabase Docker images via SUPABASE_INTERNAL_IMAGE_REGISTRY. However, this mechanism only works with public registries. There is currently no way to provide authentication credentials for registries that require login.

This limitation makes it impossible to use private or authenticated registries, such as dependency proxies, in CI environments.

Describe the solution you’d like
The Supabase CLI should support authenticated image registries by allowing users to provide registry credentials. This could be done by:

• Reusing existing Docker credentials (e.g. from docker login)
• Accepting credentials via environment variables
• Or providing a CLI configuration option for registry authentication

With this, the Supabase CLI could pull images from registries that require authentication.

Use case
In CI pipelines, I would like to use the GitLab Dependency Proxy to cache Supabase images and reduce the startup time of the Supabase environment. For example, Docker authentication in GitLab CI is typically handled via:

echo "$CI_REGISTRY_PASSWORD" | docker login -u "$CI_REGISTRY_USER" --password-stdin "$CI_REGISTRY"

The Supabase CLI currently cannot take advantage of this authenticated registry setup.

Describe alternatives you’ve considered
There is no practical alternative other than relying on public registries with generous rate limits, which is not ideal for CI environments.