Docker Build Failing with NPM Errors

engineerdawood commented 1 day ago

Bug description

Issue: Docker Installation Failing with NPM Error Despite System Upgrade

Environment:

Version: 4.0
Branch: 4.0 (confirmed up-to-date with origin/4.0)
Original System Specs: 2 vCPU, 4GB RAM
Upgraded System Specs: 4 vCPU, 8GB RAM

Problem Description: I initially attempted to build and run my project using Docker on a system with 2 vCPU and 4GB of RAM. The Docker build failed due to insufficient memory, specifically when docker is running npm commands to build Node dependencies.

To address this, I upgraded my system to 4 vCPU and 8GB of RAM. However, after multiple attempts, I am still encountering the following NPM errors during the build process.

I’ve tried rebuilding the Docker container several times, but the error persists. Can anyone provide guidance on what might be causing this issue or suggest potential solutions?

Git Status: On branch 4.0 Your branch is up to date with 'origin/4.0'.

Any help would be greatly appreciated!

superset_db | 2024-10-26 12:33:48.102 UTC [67] LOG: checkpoint starting: time superset_db | 2024-10-26 12:33:52.300 UTC [67] LOG: checkpoint complete: wrote 43 buffers (0.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=4.017 s, sync=0.013 s, total=4.199 s; sync files=11, longest=0.010 s, average=0.002 s; distance=252 kB, estimate=252 kB superset_node | npm ERR! code FETCH_ERROR superset_node | npm ERR! errno FETCH_ERROR superset_node | npm ERR! invalid json response body at https://registry.npmjs.org/@storybook%2faddon-outline reason: Invalid response body while trying to fetch https://registry.npmjs.org/@storybook%2faddon-outline: Socket timeout superset_node | superset_node | superset_node | npm ERR! A complete log of this run can be found in: superset_node | npm ERR! /root/.npm/_logs/2024-10-26T12_30_06_825Z-debug-0.log

Screenshots/recordings

No response

Superset version

4.0.2

Python version

3.11

Node version

16

Browser

Chrome

Additional context

No response

Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[x] 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[bot] commented 1 day ago

Hey @engineerdawood! I'm here to help you with any bugs, questions, or contributions you have for this project. Let's work together to solve this issue!

The issue you're encountering with the Docker build failing due to NPM errors might be related to the Node.js version you're using. For Superset 4.0.x, it's important to use Node.js version 18.x, as using an unsupported version like 16 can lead to build issues ^[1].

To resolve this, update your Dockerfile to use Node.js version 18.x. Here's a snippet you can use:

# Install nodejs for custom build
# https://nodejs.org/en/download/package-manager/
RUN set -eux; \
    curl -sL https://deb.nodesource.com/setup_18.x | bash -; \
    apt-get install -y nodejs; \
    node --version;

Make sure to rebuild your Docker container after making this change. This should help resolve the NPM errors you're experiencing.

To continue talking to Dosu, mention @dosu.

samarsrivastav commented 1 day ago

hey I am getting this error

Gracefully stopping... (press Ctrl+C again to force)
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/app/scripts/check-env.py": stat /app/scripts/check-env.py: no such file or directory: unknown

heaven890922 commented 6 hours ago

hey I am getting this error

Gracefully stopping... (press Ctrl+C again to force)
Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/app/scripts/check-env.py": stat /app/scripts/check-env.py: no such file or directory: unknown

Have you resolved this issue yet? I am also experiencing the same problem.

gokhandeveloper commented 1 hour ago

I was able to fix this by commenting out the health check in docker-compose.yml.

x-superset-user: &superset-user root
x-superset-depends-on: &superset-depends-on
  - db
  - redis
#  - superset-checks

It looks like something is up with this apache/superset-cache:3.10-slim-bookworm I tried launching it and it comes up with Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/app/scripts/check-env.py": stat /app/scripts/check-env.py: no such file or directory: unknown

apache / superset