When running docker compose up --build superset_node keeps on failing to run on Docker Desktop

[brianndjojo]

Bug description

1. git clone --depth=1 https://github.com/apache/superset.git
2. docker compose up --build

Everytime I try to restart, either by clearing the volumes or let's say by clearing the node_modules specified in the Erro rMessage: ENOTEMPTY, I still keep getting issues like the attached image. Can someone help me here?

Screenshots/recordings

Superset version

master / latest-dev

Python version

Not applicable

Node version

18 or greater

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

Hey @brianndjojo! 👋 I'm here to help you with your Docker Compose issue. I can assist with bug fixes, answer questions, and guide you on how to become a contributor.

I found a similar unsolved discussion titled "Installing dependencies in docker the process gets stuck" on the Superset GitHub repository, which might be related to your issue ^[1]. However, it does not provide a solution.

Regarding your issue with the ENOTEMPTY error during the npm build process, here are a few suggestions that might help:

1. Update npm: The logs suggest updating npm from version 10.8.2 to 11.0.0. You can do this by adding a step in your Dockerfile to update npm before running the build commands.

2. Clean up Residual Files: Ensure that all residual files and directories, especially node_modules, are completely removed before rebuilding. You can do this by running:

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

3. Check Directory Permissions: Ensure that the directory permissions are correctly set, as permission issues can sometimes cause ENOTEMPTY errors.

4. Docker Cache: Try building without using the cache to ensure that no stale files are causing the issue:

   docker-compose build --no-cache

These steps might help resolve the issue you're facing with the Docker setup for Superset.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

[hainenber]

2nd option suggested by Dosu is the key step here; it's better to clear out all files in leftover node_modules directory before rerunning.