Add new control to apache superset

[DuyAnhBD-PTIT]

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?

[dosubot[bot]]

Hi @DuyAnhBD-PTIT! I'm Dosu and I’m helping the superset team.

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).

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). 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).

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). 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.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[dosubot[bot]]

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).

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).
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).

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[DuyAnhBD-PTIT]

@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

[dosubot[bot]]

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.

Common causes are missing system dependencies (like python3, build-essential, or npm), incomplete or corrupted superset-frontend files, or node/npm version mismatches source. 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.

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.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[DuyAnhBD-PTIT]

@dosu does the default dockerfile in version 4.1.2 install all required packages?

[dosubot[bot]]

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, docs.

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.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}