[Bug] Supabase CLI v2.47.0 in proxy environment fails to pass proxy settings to edge-runtime container

[XieTianlin]

Describe the bug
supabase start fails, edge-runtime cannot connect to deno.land.
When running supabase start on an ARM64 Linux machine that requires an HTTP proxy to access the internet, the command fails. The root cause appears to be that the Supabase CLI does not correctly pass the HTTPS_PROXY environment variable to the edge-runtime container. This causes the container to fail its health checks as it cannot download its initial dependencies.

To Reproduce
Steps to reproduce the behavior:

1. Docker daemon and client are correctly configured with the proxy (confirmed via docker info and a successful curl test in a generic alpine container).
2. The Supabase edge-runtime container (public.ecr.aws/supabase/edge-runtime:v1.68.3) fails to connect.
3. Manually running the same container with proxy variables (docker run -e ...) allows the edge-runtime process to successfully fetch from the internet.
   So it seems The CLI is not passing the necessary HTTPS_PROXY environment variable to the container it creates.

Expected behavior
supabase start should honor the HTTPS_PROXY environment variable, pass it to the Docker containers (specifically edge-runtime), and start successfully.

System information

• os: Debian 13 (ARM64/aarch64)
• Supabase CLI version: 2.45.2 (also tested with 2.40.7 with the same proxy issue)
• Docker version: 28.4.0