This is an automated email from the ASF dual-hosted git repository. maximebeauchemin pushed a commit to branch docker-up in repository https://gitbox.apache.org/repos/asf/superset.git
commit 12ee660b2eea755579f4ef575a41df0013e7e61a Author: Maxime Beauchemin <[email protected]> AuthorDate: Mon Jan 19 14:18:19 2026 +0000 fix(docker): set FLASK_RUN_HOST for docker-compose-light networking Fixes Flask backend connectivity in docker-compose-light setup by setting FLASK_RUN_HOST=0.0.0.0 environment variable. Without this variable, Flask's development server only binds to 127.0.0.1 (localhost), preventing the webpack dev server container from proxying requests to the backend API. This caused health check timeouts and made the application inaccessible. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]> --- docker-compose-light.yml | 15 ++++++++++++++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/docker-compose-light.yml b/docker-compose-light.yml index b06be681af..f031b32ce8 100644 --- a/docker-compose-light.yml +++ b/docker-compose-light.yml @@ -112,12 +112,19 @@ services: superset-init-light: condition: service_completed_successfully volumes: *superset-volumes + healthcheck: + test: ["CMD-SHELL", "/app/docker/docker-healthcheck.sh"] + interval: 30s + timeout: 30s + retries: 3 + start_period: 60s environment: DATABASE_HOST: db-light DATABASE_DB: superset_light POSTGRES_DB: superset_light SUPERSET__SQLALCHEMY_EXAMPLES_URI: "duckdb:////app/data/examples.duckdb" SUPERSET_CONFIG_PATH: /app/docker/pythonpath_dev/superset_config_docker_light.py + FLASK_RUN_HOST: 0.0.0.0 GITHUB_HEAD_REF: ${GITHUB_HEAD_REF:-} GITHUB_SHA: ${GITHUB_SHA:-} @@ -154,6 +161,12 @@ services: # it'll mount and watch local files and rebuild as you update them DEV_MODE: "true" BUILD_TRANSLATIONS: ${BUILD_TRANSLATIONS:-false} + healthcheck: + test: ["CMD-SHELL", "grep -q ':2328.*0A' /proc/net/tcp || exit 1"] + interval: 10s + timeout: 5s + retries: 3 + start_period: 90s environment: # set this to false if you have perf issues running the npm i; npm run dev in-docker # if you do so, you have to run this manually on the host, which should perform better! @@ -163,7 +176,7 @@ services: # configuring the dev-server to use the host.docker.internal to connect to the backend superset: "http://superset-light:8088"; # Webpack dev server configuration - WEBPACK_DEVSERVER_HOST: "${WEBPACK_DEVSERVER_HOST:-127.0.0.1}" + WEBPACK_DEVSERVER_HOST: "${WEBPACK_DEVSERVER_HOST:-0.0.0.0}" WEBPACK_DEVSERVER_PORT: "${WEBPACK_DEVSERVER_PORT:-9000}" ports: - "${NODE_PORT:-9001}:9000" # Parameterized port, accessible on all interfaces
