Bug description

when i use git clone --depth=1 -b 4.1.2 https://github.com/apache/superset.git and docker compose -f docker-compose-non-dev.yml up -d it show error about

Screenshots/recordings

Image

Superset version

4.1.2

Python version

3.9

Node version

16

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.

Comment From: dosubot[bot]

I found some similar threads that might be relevant to your issue:

  1. Installing error - This discussion is open and might contain useful insights for installation errors [1].
  2. Issues with NPM run build version 4.1.1 - This discussion is open and addresses issues with the npm run build step, which could be similar to what you're experiencing [2].

To resolve the error during the npm run build step for Apache Superset version 4.1.2, you can try the following steps:

  1. Ensure you are using the correct versions of Node.js and npm as specified in the project's package.json file. Apache Superset requires Node.js version 20.16.0 and npm version 10.8.1. Update your Dockerfile or environment to use these versions to prevent build freezes.

  2. Add npm to the system dependencies in your Dockerfile:

RUN /app/docker/apt-install.sh build-essential python3 zstd npm
  1. Configure npm to use a mirror registry:
npm config set registry http://mirrors.ustc.edu.cn/

  1. Ensure you have the latest code by pulling from the master branch.

  2. Access Superset through port 9000 (http://localhost:9000) instead of port 8088.

  3. In docker-compose.yml, set the Superset URL to 'http://superset:8088' instead of 'http://host.docker.internal:8088'.

These changes should help resolve the 'npm run build' failure in the Docker setup by ensuring compatibility with the project's requirements and proper communication between containers [3][4].

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other

Comment From: msyavuz

Hey, Can you share the rest of the error log? It would be helpful to understand why npm run build fails.