From 2166cbdd80fb47a0bca675382bae4d95784d2de2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C4=90=E1=BB=97=20Tr=E1=BB=8Dng=20H=E1=BA=A3i?= <41283691+hainenber@users.noreply.github.com> Date: Tue, 17 Sep 2024 00:01:49 +0700 Subject: [PATCH] fix(install/docker): use zstd-baked image for building superset-frontend in containerized env (#30279) Signed-off-by: hainenber --- docker-compose.yml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/docker-compose.yml b/docker-compose.yml index fcb3503a1bc65..605be1333be5a 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -149,7 +149,14 @@ services: disable: true superset-node: - image: node:20 + build: + context: . + target: superset-node + args: + # This prevents building the frontend bundle since we'll mount local folder + # and build it on startup while firing docker-frontend.sh in dev mode, where + # it'll mount and watch local files and rebuild as you update them + DEV_MODE: "true" 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!