You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "FrancescoCastaldi (via GitHub)" <gi...@apache.org> on 2026/03/24 09:55:07 UTC
[D] Having issue with "superset-node" [superset]
GitHub user FrancescoCastaldi created a discussion: Having issue with "superset-node"
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.
GitHub link: https://github.com/apache/superset/discussions/38822
----
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] Having issue with "superset-node" [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] edited a comment on the discussion: Having issue with "superset-node"
<!-- Answer -->
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:
```bash
docker-compose down -v
docker system prune --volumes
```
Then rebuild:
```bash
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](https://github.com/apache/superset/issues/31951) with the same ENOTEMPTY error during npm install in the superset-frontend container.
<!-- 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=9f74f064-21e7-4591-b538-8ea6b6cd27e2) [](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/38822#discussioncomment-16291007
----
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] Having issue with "superset-node" [superset]
Posted by "dosubot[bot] (via GitHub)" <gi...@apache.org>.
GitHub user dosubot[bot] added a comment to the discussion: Having issue with "superset-node"
<!-- Answer -->
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:
```bash
docker-compose down -v
docker system prune --volumes
```
Then rebuild:
```bash
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](https://github.com/apache/superset/issues/31951) with the same ENOTEMPTY error during npm install in the superset-frontend container.
<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=brand-link).*
---
<sup>How did I do? [Good](https://app.dosu.dev/response-feedback/9f74f064-21e7-4591-b538-8ea6b6cd27e2?feedback_type=great_response&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/9f74f064-21e7-4591-b538-8ea6b6cd27e2?feedback_type=irrelevant_answer&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/9f74f064-21e7-4591-b538-8ea6b6cd27e2?feedback_type=incorrect_sources&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/9f74f064-21e7-4591-b538-8ea6b6cd27e2?feedback_type=too_verbose&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/9f74f064-21e7-45
91-b538-8ea6b6cd27e2?feedback_type=hallucination&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/9f74f064-21e7-4591-b538-8ea6b6cd27e2?feedback_type=bug_report&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-bug_report) | [Other](https://app.dosu.dev/response-feedback/9f74f064-21e7-4591-b538-8ea6b6cd27e2?feedback_type=other&utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=feedback-other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=chat-badge) [](https://cursor.com/link/prompt?text=This%20is%20a%20known%20issue%20caused%20by%20residual%20Docker%20volumes%20from%20previous%20builds%20conflicting%20with%20npm%27s%20rename%20operations.%20Simply%20removing%20the%20%60node_modules%60%20folder%20isn%27t%20enough%E2%80%94you%20need%20to%20clean%20up%20the%20Docker%20volumes%20as%20well.%0A%0ATry%20running%20these%20commands%3A%0A%0A%60%60%60bash%0Adocker-compose%20down%20-v%0Adocker%20system%20prune%20--volumes%0A%60%60%60%0A%0AThen%20rebuild%3A%0A%0A%60%60%60bash%0Adocker%20compose%20up%20--build%0A%60%60%60%0A%0A%2A%2ANote%3A%2A%2A%20%60docker%20system%20prune%20--volumes%60%20removes%20all%20unused%20volumes%20system-wide%2C%20so%20be%20careful%20if%20you%2
0have%20other%20Docker%20projects%20with%20data%20you%20want%20to%20preserve.%20If%20that%27s%20a%20concern%2C%20you%20can%20try%20just%20%60docker-compose%20down%20-v%60%20first%20to%20only%20remove%20Superset-related%20volumes.%0A%0AThis%20issue%20was%20%5Breported%20previously%5D%28https%3A//github.com/apache/superset/issues/31951%29%20with%20the%20same%20ENOTEMPTY%20error%20during%20npm%20install%20in%20the%20superset-frontend%20container.) [](https://go.dosu.dev/discord-bot?utm_source=github&utm_medium=bot-comment&utm_campaign=github-assistant&utm_content=join-discord) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/38822)
GitHub link: https://github.com/apache/superset/discussions/38822#discussioncomment-16291007
----
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] Having issue with "superset-node" [superset]
Posted by "FrancescoCastaldi (via GitHub)" <gi...@apache.org>.
GitHub user FrancescoCastaldi added a comment to the discussion: Having issue with "superset-node"
not working this fix...
GitHub link: https://github.com/apache/superset/discussions/38822#discussioncomment-16291670
----
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