You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "DuyAnhBD-PTIT (via GitHub)" <gi...@apache.org> on 2025/10/08 12:37:37 UTC
[D] Add new control to apache superset [superset]
GitHub user DuyAnhBD-PTIT created a discussion: Add new control to apache superset
I was tasked with adding a customized control to the control panel but when I try to mount it to the superset_app nothing happens, it still use the old build from the container, my frontend changes doesn't get apply at all, I tried to build locally and copying it to the docker but it doesn't work. How do I get the docker to use my newly changed superset-frontend code?
GitHub link: https://github.com/apache/superset/discussions/35571
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "nick0258 (via GitHub)" <gi...@apache.org>.
GitHub user nick0258 added a comment to the discussion: Add new control to apache superset
@DuyAnhBD-PTIT
What I understand is when you change something in superset-frontend, the Docker container still shows the old UI.
That’s because Superset serves pre-built static files, not your local source files.
I faced the same issue in docker, and I fixed it by performing the following steps.
You need to rebuild the frontend and copy the new build into the container.
Step 1. Build the frontend in your local system.
cd superset-frontend
npm install
npm run build
Step 2. Copy the new build from the local system to Docker.
Create a custom Dockerfile:
FROM apache/superset:latest
USER root
#Copy your updated frontend
COPY superset-frontend/ /app/superset-frontend/
#Rebuild inside container
RUN cd /app/superset-frontend && \
npm ci && npm run build && \
cp -r /app/superset-frontend/build/* /app/superset/static/assets/
USER superset
Step 3: After then rebuild the docker image and run:
docker build -t custom-superset .
docker run -d -p 8088:8088 custom-superset
Please let me know if you’re still facing the issue. I’ll check the possible ways to fix it and share the solution here.
Nick R -
Cloud Team Lead - Accuweb.cloud
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14673189
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "DuyAnhBD-PTIT (via GitHub)" <gi...@apache.org>.
GitHub user DuyAnhBD-PTIT added a comment to the discussion: Add new control to apache superset
@dosu running the dev-server and accessing localhost:9000 returns this:
<img width="2550" height="1024" alt="image" src="https://github.com/user-attachments/assets/64a33a49-c0f0-4a9b-a156-a15ec7689ad5" />
Is there a way for my changes in superset-frontend to be directly applied when building the container?
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626226
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Add new control to apache superset
<!-- Answer -->
The error at RUN npm run ${BUILD_CMD} usually means the frontend build failed inside Docker. In Superset 4.1.2, BUILD_CMD defaults to build, which runs the build script in superset-frontend/package.json (webpack in production mode) [source](https://github.com/apache/superset/blob/master/superset-frontend/package.json).
Common causes are missing system dependencies (like python3, build-essential, or npm), incomplete or corrupted superset-frontend files, or node/npm version mismatches [source](https://github.com/apache/superset/issues/31714). Make sure your Dockerfile installs all required packages (RUN apt-get install -y python3 make gcc g++ npm), and that your superset-frontend directory is complete and up to date. Also, check that node is v20.x and npm is v10.x as required by package.json.
To troubleshoot: check the full npm error logs in the Docker build output for the real cause. Try running npm run prune in superset-frontend to clean node_modules, then rebuild with docker compose up --build. If the build still fails, you can build the frontend assets locally with npm before running Docker compose as a workaround [source](https://github.com/apache/superset/issues/32187).
If you want more verbose logs, you can add --verbose to the npm run command in the Dockerfile to see more details about the failure.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=211ab97f-d615-4271-909d-9d6095abc0ea) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626437
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "DuyAnhBD-PTIT (via GitHub)" <gi...@apache.org>.
GitHub user DuyAnhBD-PTIT deleted a comment on the discussion: Add new control to apache superset
@dosu guide me step by step for version 4.1.2, I have tried the suggested fix but It doesn't work, the local folder is mounted properly but my edits are not being recognized
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626075
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Add new control to apache superset
<!-- Answer -->
Your errors are likely caused by a mismatch between your checked-out code and the Docker image build context, or by Docker using the wrong Dockerfile or stale build cache. The Superset 4.1.2 Dockerfile does define both the `PY_VER` argument and the `dev` build stage as expected, so these errors usually mean Docker isn't seeing the right files or context ([Dockerfile reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/Dockerfile)).
Here's how to resolve this:
1. Make sure your local repo is checked out to the exact `4.1.2` tag and you haven't modified the Dockerfile or compose files.
2. Run `docker system prune -af` and `docker builder prune -af` to clear any stale build cache or images.
3. Run `docker compose down -v` to remove old volumes.
4. From the project root, run `docker compose up --build` (or specify the compose file and Dockerfile explicitly if needed).
5. Double-check that your compose file isn't mounting a local `docker/` directory that could override scripts inside the image ([discussion](https://github.com/apache/superset/issues/31510)).
6. If you still see the error, try cloning a fresh copy of the 4.1.2 release in a new directory and building there.
These steps should ensure Docker uses the correct build context and files, resolving the `PY_VER` and `dev` stage errors. If you run into npm or frontend build issues, make sure your local `superset-frontend` directory is complete and up to date, and that your Dockerfile uses Node 20.x for frontend builds ([node version reference](https://github.com/apache/superset/issues/34577)).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=82aa6146-c5f7-4f0d-bc7d-9294fea257a1) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626305
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Add new control to apache superset
<!-- Answer -->
The garbled output at localhost:9000 was caused by a recent change where the dev server started using zstd encoding, which wasn't handled in the webpack proxy config. This has been fixed—make sure your superset-frontend is up to date so the dev server decompresses zstd data correctly and the page renders as expected [details](https://github.com/apache/superset/pull/30034).
For your changes in superset-frontend to be directly applied when running in Docker, use the default Docker Compose dev setup: it mounts your local superset-frontend folder into the container, so edits are reflected live. Just run docker compose up --build to ensure everything is rebuilt, and access the app at http://localhost:9000 (not 8088) for hot-reloading [docs](https://github.com/apache/superset/blob/master/docs/docs/contributing/development.mdx). If you run into npm issues, try npm run prune in superset-frontend or set NPM_RUN_PRUNE=true before starting Docker.
If you want to build the frontend inside the container, make sure BUILD_SUPERSET_FRONTEND_IN_DOCKER=true in docker/.env (the default), and Docker will handle npm install and npm run dev-server for you [script](https://github.com/apache/superset/blob/master/docker/docker-frontend.sh).
In short: update your superset-frontend, use docker compose up --build, and access via port 9000 for live frontend changes.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/ffc3518c-5f33-4d0c-aec4-ec3c69c9f913?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/ffc3518c-5f33-4d0c-aec4-ec3c69c9f913?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/ffc3518c-5f33-4d0c-aec4-ec3c69c9f913?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/ffc3518c-5f33-4d0c-aec4-ec3c69c9f913?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/ffc3518c-5f33-4d0c-aec4-ec3c69c9f913?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/ffc3518c-5f33-4d0c-aec4-ec3c69c9f913?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/ffc3518c-5f33-4d0c-aec4-ec3c69c9f913?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/35571)
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626246
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Add new control to apache superset
<!-- Answer -->
Your errors are likely caused by a mismatch between your checked-out code and the Docker image build context, or by Docker using the wrong Dockerfile or stale build cache. The Superset 4.1.2 Dockerfile does define both the `PY_VER` argument and the `dev` build stage as expected, so these errors usually mean Docker isn't seeing the right files or context ([Dockerfile reference](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/Dockerfile)).
Here's how to resolve this:
1. Make sure your local repo is checked out to the exact `4.1.2` tag and you haven't modified the Dockerfile or compose files.
2. Run `docker system prune -af` and `docker builder prune -af` to clear any stale build cache or images.
3. Run `docker compose down -v` to remove old volumes.
4. From the project root, run `docker compose up --build` (or specify the compose file and Dockerfile explicitly if needed).
5. Double-check that your compose file isn't mounting a local `docker/` directory that could override scripts inside the image ([discussion](https://github.com/apache/superset/issues/31510)).
6. If you still see the error, try cloning a fresh copy of the 4.1.2 release in a new directory and building there.
These steps should ensure Docker uses the correct build context and files, resolving the `PY_VER` and `dev` stage errors. If you run into npm or frontend build issues, make sure your local `superset-frontend` directory is complete and up to date, and that your Dockerfile uses Node 20.x for frontend builds ([node version reference](https://github.com/apache/superset/issues/34577)).
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/82aa6146-c5f7-4f0d-bc7d-9294fea257a1?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/82aa6146-c5f7-4f0d-bc7d-9294fea257a1?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/82aa6146-c5f7-4f0d-bc7d-9294fea257a1?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/82aa6146-c5f7-4f0d-bc7d-9294fea257a1?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/82aa6146-c5f7-4f0d-bc7d-9294fea257a1?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/82aa6146-c5f7-4f0d-bc7d-9294fea257a1?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/82aa6146-c5f7-4f0d-bc7d-9294fea257a1?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/35571)
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626305
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "DuyAnhBD-PTIT (via GitHub)" <gi...@apache.org>.
GitHub user DuyAnhBD-PTIT added a comment to the discussion: Add new control to apache superset
@dosu guide me step by step for version 4.1.2, I have tried the suggested fix but It doesn't work, the local folder is mounted properly but my edits are not being recognized
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626075
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Add new control to apache superset
<!-- Greeting -->
Hi @DuyAnhBD-PTIT! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
To get your frontend changes to show up in Superset running in Docker, make sure you’re not accidentally overriding your new build with a local volume mount. If you’re using Docker Compose in development mode, by default the local `superset-frontend` folder is mounted into the container, so edits you make locally should reflect in real time. If you want Docker to use a new build, check your `docker-compose` volumes section and remove or adjust any mounts that might override the container’s code with your local files ([source](https://github.com/apache/superset/discussions/35458)).
For development, the frontend is usually built inside the container with `npm install` and `npm run dev-server`, serving assets at http://localhost:9000. Make sure you’re accessing the app through that port for live reloads ([source](https://github.com/apache/superset/issues/32178)). If you want to build the frontend outside Docker (for example, if Docker builds are slow), set `BUILD_SUPERSET_FRONTEND_IN_DOCKER=false` in `docker/.env` and run `npm i && npm run dev` locally ([source](https://github.com/apache/superset/blob/master/docs/docs/installation/docker-compose.mdx)).
If you’re still seeing the old build, try running `docker compose up --build` to force Docker to rebuild everything and clear any cached layers ([source](https://github.com/apache/superset/blob/master/docs/docs/installation/docker-compose.mdx)). If you run into npm issues, run `npm run prune` in `superset-frontend/` or set `NPM_RUN_PRUNE=true` before starting Docker.
In summary: check your volume mounts, use the right port for frontend dev, and rebuild with `docker compose up --build` to ensure your changes are picked up.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9f582f19-6f09-4ebc-8b3b-35470d10006b?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9f582f19-6f09-4ebc-8b3b-35470d10006b?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9f582f19-6f09-4ebc-8b3b-35470d10006b?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9f582f19-6f09-4ebc-8b3b-35470d10006b?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9f582f19-6f09-4ebc-8b3b-35470d10006b?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9f582f19-6f09-4ebc-8b3b-35470d10006b?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/9f582f19-6f09-4ebc-8b3b-35470d10006b?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/35571)
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14625896
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Add new control to apache superset
<!-- Answer -->
The error at RUN npm run ${BUILD_CMD} usually means the frontend build failed inside Docker. In Superset 4.1.2, BUILD_CMD defaults to build, which runs the build script in superset-frontend/package.json (webpack in production mode) [source](https://github.com/apache/superset/blob/master/superset-frontend/package.json).
Common causes are missing system dependencies (like python3, build-essential, or npm), incomplete or corrupted superset-frontend files, or node/npm version mismatches [source](https://github.com/apache/superset/issues/31714). Make sure your Dockerfile installs all required packages (RUN apt-get install -y python3 make gcc g++ npm), and that your superset-frontend directory is complete and up to date. Also, check that node is v20.x and npm is v10.x as required by package.json.
To troubleshoot: check the full npm error logs in the Docker build output for the real cause. Try running npm run prune in superset-frontend to clean node_modules, then rebuild with docker compose up --build. If the build still fails, you can build the frontend assets locally with npm before running Docker compose as a workaround [source](https://github.com/apache/superset/issues/32187).
If you want more verbose logs, you can add --verbose to the npm run command in the Dockerfile to see more details about the failure.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/211ab97f-d615-4271-909d-9d6095abc0ea?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/211ab97f-d615-4271-909d-9d6095abc0ea?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/211ab97f-d615-4271-909d-9d6095abc0ea?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/211ab97f-d615-4271-909d-9d6095abc0ea?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/211ab97f-d615-4271-909d-9d6095abc0ea?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/211ab97f-d615-4271-909d-9d6095abc0ea?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/211ab97f-d615-4271-909d-9d6095abc0ea?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/35571)
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626437
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Add new control to apache superset
<!-- Answer -->
The default Dockerfile in Superset 4.1.2 installs most core system and Python dependencies needed for development and building the frontend and backend. It sets up Node.js, npm, build-essential tools, and installs Python packages from requirements files. However, it does not include all database drivers (like MSSQL, PostgreSQL, or Redis) by default—you need to extend the image and install those explicitly for your environment. For production, it's recommended to build your own image based on the default and add the drivers you need [reference](https://github.com/apache/superset/discussions/33957), [docs](https://github.com/apache/superset/blob/master/docs/docs/installation/docker-builds.mdx).
If your build fails at the frontend step (`npm run build`), check for missing system dependencies or incompatible Node/npm versions. The Dockerfile uses Node 20.x and expects npm 10.x, matching the frontend's package.json requirements. For database connectivity, add drivers like `psycopg2-binary`, `mysqlclient`, or others as needed for your setup.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Share context across your team and agents. Try [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-feedback&utm_term=apache%2Fsuperset&message_id=b1f4ef92-07ca-4a8b-8b7d-439ecf3bca2a) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-learn-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=knowledge-infrastructure-add-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14632211
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Add new control to apache superset
<!-- Greeting -->
Hi @DuyAnhBD-PTIT! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the superset team.
<!-- Answer -->
To get your frontend changes to show up in Superset running in Docker, make sure you’re not accidentally overriding your new build with a local volume mount. If you’re using Docker Compose in development mode, by default the local `superset-frontend` folder is mounted into the container, so edits you make locally should reflect in real time. If you want Docker to use a new build, check your `docker-compose` volumes section and remove or adjust any mounts that might override the container’s code with your local files ([source](https://github.com/apache/superset/discussions/35458)).
For development, the frontend is usually built inside the container with `npm install` and `npm run dev-server`, serving assets at http://localhost:9000. Make sure you’re accessing the app through that port for live reloads ([source](https://github.com/apache/superset/issues/32178)). If you want to build the frontend outside Docker (for example, if Docker builds are slow), set `BUILD_SUPERSET_FRONTEND_IN_DOCKER=false` in `docker/.env` and run `npm i && npm run dev` locally ([source](https://github.com/apache/superset/blob/master/docs/docs/installation/docker-compose.mdx)).
If you’re still seeing the old build, try running `docker compose up --build` to force Docker to rebuild everything and clear any cached layers ([source](https://github.com/apache/superset/blob/master/docs/docs/installation/docker-compose.mdx)). If you run into npm issues, run `npm run prune` in `superset-frontend/` or set `NPM_RUN_PRUNE=true` before starting Docker.
In summary: check your volume mounts, use the right port for frontend dev, and rebuild with `docker compose up --build` to ensure your changes are picked up.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=9f582f19-6f09-4ebc-8b3b-35470d10006b) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14625896
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "DuyAnhBD-PTIT (via GitHub)" <gi...@apache.org>.
GitHub user DuyAnhBD-PTIT added a comment to the discussion: Add new control to apache superset
@dosu Dockerfile:50
--------------------
48 | # Runs the webpack build process
49 | COPY superset-frontend /app/superset-frontend
50 | >>> RUN npm run ${BUILD_CMD}
51 |
52 | # This copies the .po files needed for translation
--------------------
target superset-init: failed to solve: process "/bin/sh -c npm run ${BUILD_CMD}" did not complete successfully: exit code: 1
View build details: docker-desktop://dashboard/build/default/default/l3in5ijtlox0r52jlr373yy20
problem when running docker compose up --build version 4.1.2 with no changes to the dockerfile
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626422
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "DuyAnhBD-PTIT (via GitHub)" <gi...@apache.org>.
GitHub user DuyAnhBD-PTIT added a comment to the discussion: Add new control to apache superset
@dosu version 4.1.2 encountering this message when running docker compose up --build
[+] Building 1.2s (4/4) FINISHED
=> [internal] load local bake definitions 0.0s
=> => reading from stdin 2.78kB 0.0s
=> [superset-worker-beat internal] load build definition from Dockerfile 0.0s
=> => transferring dockerfile: 2.35kB 0.0s
=> WARN: InvalidDefaultArgInFrom: Default value for ARG python:${PY_VER} results in empty or invalid base image name (line 21) 0.0s
=> WARN: InvalidDefaultArgInFrom: Default value for ARG python:${PY_VER} results in empty or invalid base image name (line 21) 0.0s
=> WARN: InvalidDefaultArgInFrom: Default value for ARG python:${PY_VER} results in empty or invalid base image name (line 21) 0.0s
=> WARN: InvalidDefaultArgInFrom: Default value for ARG python:${PY_VER} results in empty or invalid base image name (line 21) 0.0s
=> WARN: UndefinedArgInFrom: FROM argument 'PY_VER' is not declared (line 21) 0.0s
=> WARN: UndefinedArgInFrom: FROM argument 'PY_VER' is not declared (line 21) 0.0s
=> WARN: UndefinedArgInFrom: FROM argument 'PY_VER' is not declared (line 21) 0.0s
=> WARN: UndefinedArgInFrom: FROM argument 'PY_VER' is not declared (line 21) 0.0s
=> [superset-websocket internal] load build definition from Dockerfile 0.1s
=> => transferring dockerfile: 1.24kB 0.0s
=> WARN: FromAsCasing: 'as' and 'FROM' keywords' casing do not match (line 15) 0.1s
=> CANCELED [superset-websocket internal] load metadata for docker.io/library/node:16-alpine 0.1s
target superset-worker-beat: failed to solve: target stage "dev" could not be found
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626263
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Add new control to apache superset
<!-- Answer -->
The default Dockerfile in Superset 4.1.2 installs most core system and Python dependencies needed for development and building the frontend and backend. It sets up Node.js, npm, build-essential tools, and installs Python packages from requirements files. However, it does not include all database drivers (like MSSQL, PostgreSQL, or Redis) by default—you need to extend the image and install those explicitly for your environment. For production, it's recommended to build your own image based on the default and add the drivers you need [reference](https://github.com/apache/superset/discussions/33957), [docs](https://github.com/apache/superset/blob/master/docs/docs/installation/docker-builds.mdx).
If your build fails at the frontend step (`npm run build`), check for missing system dependencies or incompatible Node/npm versions. The Dockerfile uses Node 20.x and expects npm 10.x, matching the frontend's package.json requirements. For database connectivity, add drivers like `psycopg2-binary`, `mysqlclient`, or others as needed for your setup.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/b1f4ef92-07ca-4a8b-8b7d-439ecf3bca2a?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/b1f4ef92-07ca-4a8b-8b7d-439ecf3bca2a?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/b1f4ef92-07ca-4a8b-8b7d-439ecf3bca2a?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/b1f4ef92-07ca-4a8b-8b7d-439ecf3bca2a?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b1f4ef92-07ca-4a8b-8b7d-439ecf3bca2a?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/b1f4ef92-07ca-4a8b-8b7d-439ecf3bca2a?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/b1f4ef92-07ca-4a8b-8b7d-439ecf3bca2a?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&
nbsp;[](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/35571)
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14632211
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "DuyAnhBD-PTIT (via GitHub)" <gi...@apache.org>.
GitHub user DuyAnhBD-PTIT added a comment to the discussion: Add new control to apache superset
@dosu does the default dockerfile in version 4.1.2 install all required packages?
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14632206
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org
Re: [D] Add new control to apache superset [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Add new control to apache superset
<!-- Answer -->
The garbled output at localhost:9000 was caused by a recent change where the dev server started using zstd encoding, which wasn't handled in the webpack proxy config. This has been fixed—make sure your superset-frontend is up to date so the dev server decompresses zstd data correctly and the page renders as expected [details](https://github.com/apache/superset/pull/30034).
For your changes in superset-frontend to be directly applied when running in Docker, use the default Docker Compose dev setup: it mounts your local superset-frontend folder into the container, so edits are reflected live. Just run docker compose up --build to ensure everything is rebuilt, and access the app at http://localhost:9000 (not 8088) for hot-reloading [docs](https://github.com/apache/superset/blob/master/docs/docs/contributing/development.mdx). If you run into npm issues, try npm run prune in superset-frontend or set NPM_RUN_PRUNE=true before starting Docker.
If you want to build the frontend inside the container, make sure BUILD_SUPERSET_FRONTEND_IN_DOCKER=true in docker/.env (the default), and Docker will handle npm install and npm run dev-server for you [script](https://github.com/apache/superset/blob/master/docker/docker-frontend.sh).
In short: update your superset-frontend, use docker compose up --build, and access via port 9000 for live frontend changes.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=reply-with-mention&utm_term=apache%2Fsuperset).*
---
Docs are dead. Just use [Dosu](https://dosu.dev?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-tagline&utm_term=apache%2Fsuperset).
[](https://app.dosu.dev/response-feedback?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-feedback&utm_term=apache%2Fsuperset&message_id=ffc3518c-5f33-4d0c-aec4-ec3c69c9f913) [](https://github.dosu.com/apache/superset?utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-ask-repo&utm_term=apache%2Fsuperset) [](https://app.dosu.dev/signup?referrer=openSource&source=github-footer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-comment-footer-20260415&utm_content=static-docs-share-team&utm_term=apache%2Fsuperset)
GitHub link: https://github.com/apache/superset/discussions/35571#discussioncomment-14626246
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org