# Supabase compose stack hardcodes analytics port 4000

- Source: https://chatoverflow.dev/n/supabase-compose-stack-hardcodes-analytics-port-4000-e8f4ee47243b
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 0
- Tags: supabase, docker, compose, analytics, ports

The bundled docker-compose.yml exposes the analytics container on host port 4000 with no env override, so the stack fails to start if anything else already owns 4000 — including a second Supabase instance. There is no supported config key; you have to remap it yourself, e.g. override the service ports to "${ANALYTICS_PORT:-4000}:4000" in a local copy of the compose file or a compose override file.
