Having issue with "superset-node"

[FrancescoCastaldi]

Hi, I’m currently having an issue with turning up the post‑build superset-node service, with this error:
Attaching to superset-node-1
superset-node-1 | Building Superset frontend in dev mode inside docker container
superset-node-1 | Running "npm install"
superset-node-1 | npm warn EBADENGINE Unsupported engine {
...
superset-node-1 | npm error code ENOTEMPTY
superset-node-1 | npm error syscall rename
superset-node-1 | npm error path /app/superset-frontend/packages/generator-superset/node_modules/ejs
superset-node-1 | npm error dest /app/superset-frontend/packages/generator-superset/node_modules/.ejs-ATRb5iqJ
superset-node-1 | npm error errno -39
superset-node-1 | npm error ENOTEMPTY: directory not empty, rename '/app/superset-frontend/packages/generator-superset/node_modules/ejs' -> '/app/superset-frontend/packages/generator-superset/node_modules/.ejs-ATRb5iqJ'
superset-node-1 | npm error A complete log of this run can be found in: /root/.npm/_logs/2026-03-24T09_52_43_402Z-debug-0.log
superset-node-1 exited with code 217

How can I fix it? I already removed the node_modules folder and rebuilt it, but the service still won’t start.

[dosubot[bot]]

This is a known issue caused by residual Docker volumes from previous builds conflicting with npm's rename operations. Simply removing the node_modules folder isn't enough—you need to clean up the Docker volumes as well.

Try running these commands:

docker-compose down -v
docker system prune --volumes

Then rebuild:

docker compose up --build

Note: docker system prune --volumes removes all unused volumes system-wide, so be careful if you have other Docker projects with data you want to preserve. If that's a concern, you can try just docker-compose down -v first to only remove Superset-related volumes.

This issue was reported previously with the same ENOTEMPTY error during npm install in the superset-frontend container.

To reply, just mention @dosu.

---

Share context across your team and agents. Try Dosu.

[FrancescoCastaldi]

not working this fix...