Deno.env.get('SUPABASE_URL') -> 'http://kong:8000'

[k-nearest-neighbor]

When using supabase start or supabase functions serve the SUPABASE_URL env var inside the function which as far as I can tell is managed only by supabase is set to 'http://kong:8000'

(Maybe this is intended? I realize kong is supposed to be a gateway -- but when supabase start is running, kong is not resolving)

To Reproduce Steps to reproduce the behavior:

• SUPABASE_URL is not set in .env (it shouldn't be afik)
• Nothing unusual in config.toml (as far as I know)

1. supabase start or supabase functions serve
2. Inside function index.ts console.log('suabaseUrl: ' + Deno.env.get('SUPABASE_URL'))

[Info] supabaseUrl: http://kong:8000

Expected behavior I believe this should be the api url? Like http://127.0.0.1:54321

System information

• Version of OS: MacOS Sonoma 14.6
• Version of CLI:supabase -v 1.200.3
• Version of Docker:docker -v Docker version 27.1.1, build 6312585
• Versions of services: [output from supabase services command]

      SERVICE IMAGE      │      LOCAL       │   LINKED
  ─────────────────────────┼──────────────────┼─────────────
  supabase/postgres      │ 15.6.1.115       │ 15.6.1.115
  supabase/gotrue        │ v2.162.1         │ v2.162.1
  postgrest/postgrest    │ v12.2.3          │ v12.2.3
  supabase/realtime      │ v2.30.34         │ -
  supabase/storage-api   │ v1.11.7          │ v1.11.7
  supabase/edge-runtime  │ v1.58.3          │ -
  supabase/studio        │ 20240729-ce42139 │ -
  supabase/postgres-meta │ v0.83.2          │ -
  supabase/logflare      │ 1.4.0            │ -
  supabase/supavisor     │ 1.1.56           │ -

[k-nearest-neighbor]

I guess that is what it is supposed to be. 'kong' I guess is a hostname that resolves inside the containers. The documentation isn't super clear that you should expect SUPABASE_URL to be set to this when running locally