You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@superset.apache.org by ma...@apache.org on 2026/01/20 15:19:18 UTC
(superset) branch docker-up updated (68405e9397 -> 5ff5dc2aad)
This is an automated email from the ASF dual-hosted git repository.
maximebeauchemin pushed a change to branch docker-up
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 68405e9397 fix(docker): set FLASK_RUN_HOST for docker-compose-light networking
new 5ff5dc2aad fix(docker): set FLASK_RUN_HOST for docker-compose-light networking
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (68405e9397)
\
N -- N -- N refs/heads/docker-up (5ff5dc2aad)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
docker-compose-light.yml | 3 +++
1 file changed, 3 insertions(+)
(superset) 01/01: fix(docker): set FLASK_RUN_HOST for docker-compose-light networking
Posted by ma...@apache.org.
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 5ff5dc2aad3722acc0c049ad6fb326575c16f0a7
Author: Maxime Beauchemin <ma...@gmail.com>
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 <no...@anthropic.com>
---
docker-compose-light.yml | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/docker-compose-light.yml b/docker-compose-light.yml
index b06be681af..2d35952037 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,9 @@ services:
# it'll mount and watch local files and rebuild as you update them
DEV_MODE: "true"
BUILD_TRANSLATIONS: ${BUILD_TRANSLATIONS:-false}
+ depends_on:
+ superset-light:
+ condition: service_healthy
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!