Supavisor cannot resolve IPV6

[Hdnaye]

Bug report

Describe the bug

Using the self-hosted Supabase template on Railway : https://railway.com/template/supabase.

After adding this Supavisor repository to Railway: https://github.com/supabase/supavisor (since it is not included in the template above)

Supavisor cannot resolve IPV6 domains, preventing me from using Railway's internal network.

To Reproduce

I did set expected variables in the Supavisor Container:

ECTO_IPV6=true API_JWT_SECRET METRICS_JWT_SECRET VAULT_ENC_KEY SECRET_KEY_BASE DATABASE_URL=ecto://${DB_USER}:${DB_PASSWORD}@${DB_HOST}:5432/${DB_NAME}

DB_HOST being Railway's internal network address for my PostgreSQL db.

Error raised by Supavisor: 12:52:10.438 [error] Postgrex.Protocol (#PID<0.3326.0>) failed to connect: ** (DBConnection.ConnectionError) tcp connect (postgres-ts0p.railway.internal:5432): non-existing domain - :nxdomain

Expected behavior

I want Supavisor to connect to my database using Railway's internal network (thus use IPV6)