dosubot[bot] commented on issue #33686: URL: https://github.com/apache/superset/issues/33686#issuecomment-2938982111
<!-- Answer --> You've already set `PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true`, which is the correct variable for Superset's Docker build process. However, the error message from Puppeteer still references `PUPPETEER_SKIP_DOWNLOAD`, which suggests that the underlying Puppeteer install script is not seeing the skip variable as expected. There are a few other causes and workarounds based on recent issues and the current Superset Docker setup: 1. **Ensure npm is installed in the build environment**: Some users have resolved similar issues by explicitly adding `npm` to the list of packages installed in the Docker build step. In your Dockerfile or in the `/app/docker/apt-install.sh` invocation, make sure you include `npm` (e.g., `RUN /app/docker/apt-install.sh build-essential python3 zstd npm`). This ensures the right npm binary is available and can sometimes resolve environment propagation issues during `npm ci` [source](https://github.com/apache/superset/issues/31714). 2. **Check Node and npm version compatibility**: Superset's `package.json` specifies required versions for Node and npm. Make sure your Docker image matches these versions. For recent Superset, Node 20.x and npm 10.x are expected. If you see npm version warnings, try updating npm inside the Docker container with `npm install -g npm@<expected-version>` before running `npm ci` [source](https://github.com/apache/superset/issues/33050). 3. **Try building the frontend outside Docker**: Set `BUILD_SUPERSET_FRONTEND_IN_DOCKER=false` in your `.env` and build the frontend locally on your host machine (run `npm install` and `npm run build` in `superset-frontend/`), then proceed with the Docker build. This can bypass resource or compatibility issues inside the container [source](https://github.com/apache/superset/issues/32426). 4. **Mirror npm registry**: If you are behind a firewall or have network restrictions, configure npm to use a mirror registry (e.g., `npm config set registry http://registry.npmjs.org/` or a local/country mirror) [source](https://github.com/apache/superset/issues/31714). 5. **Environment variable propagation**: While Superset uses `PUPPETEER_SKIP_CHROMIUM_DOWNLOAD`, Puppeteer itself checks for `PUPPETEER_SKIP_DOWNLOAD`. To be safe, set both variables to `true` in your Dockerfile and `.env` (as you have tried), and also pass them explicitly in the `environment` section of your Docker Compose service definitions for any service that builds or runs the frontend. 6. **Clean up old node_modules and caches**: Sometimes, stale `node_modules` or npm/yarn caches can cause unexpected behavior. Ensure you are starting from a clean state by removing any cached layers, deleting `node_modules`, and clearing npm/yarn caches before building. If you try these steps and still encounter the error, please share the exact Dockerfile section and build logs after making these changes, as there may be a subtle issue with how the environment is being passed or with the specific Puppeteer version in use. <!-- Dosu Comment Footer --> *To reply, just mention my name [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/c3f65605-00f4-458f-ac87-c0bd9131de0e?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c3f65605-00f4-458f-ac87-c0bd9131de0e?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c3f65605-00f4-458f-ac87-c0bd9131de0e?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c3f65605-00f4-458f-ac87-c0bd9131de0e?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c3f65605-00f4-458f-ac87-c0bd9131de0e?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c3f65605-00f4-458f-ac87-c0bd9131de0e?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c3f65605-00f4-458f-ac87-c0bd9131de0e?feedback_type=other)</sup> [](https://go.dosu.dev/discord-bot) [! [Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/issues/33686) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
