dosubot[bot] commented on issue #33686:
URL: https://github.com/apache/superset/issues/33686#issuecomment-2938910115

   <!-- Answer -->
   The issue is caused by a mismatch between the environment variable you are 
setting and the one actually used by Superset's Docker build scripts. 
Superset's Docker build process uses PUPPETEER_SKIP_CHROMIUM_DOWNLOAD (not 
PUPPETEER_SKIP_DOWNLOAD) to control whether Puppeteer attempts to download 
Chromium during the frontend build. This is set in both the Dockerfile and the 
default `.env` file in the repository, and is checked by the build scripts 
themselves 
([Dockerfile](https://github.com/apache/superset/blob/20519158d2ab6325f7564b16615a99fe0ebe7a38/Dockerfile),
 
[docker/.env](https://github.com/apache/superset/blob/20519158d2ab6325f7564b16615a99fe0ebe7a38/docker/.env),
 
[docker/docker-frontend.sh](https://github.com/apache/superset/blob/20519158d2ab6325f7564b16615a99fe0ebe7a38/docker/docker-frontend.sh)).
   
   To resolve your issue, ensure that you are setting 
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true in your `docker/.env` file and in any 
relevant Docker Compose environment sections. You do not need to set 
PUPPETEER_SKIP_DOWNLOAD, as it is not referenced by Superset's Docker build 
process.
   
   If you already have PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true in your `.env` 
file (as shown in your config), you can remove any references to 
PUPPETEER_SKIP_DOWNLOAD from your Docker Compose YAML and environment. Then 
rebuild your containers. This should prevent Puppeteer from attempting to 
download Chromium during the build.
   
   If you continue to see the error, double-check that your build context is 
correct and that no other scripts or dependencies are overriding this variable. 
The official Superset Docker build scripts and Dockerfile are designed to skip 
the Chromium download when PUPPETEER_SKIP_CHROMIUM_DOWNLOAD is set to true.
   
   
   <!-- 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/be05b43b-fec3-428f-b6b1-f5850448b2ce?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/be05b43b-fec3-428f-b6b1-f5850448b2ce?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/be05b43b-fec3-428f-b6b1-f5850448b2ce?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/be05b43b-fec3-428f-b6b1-f5850448b2ce?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/be05b43b-fec3-428f-b6b1-f5850448b2ce?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/be05b43b-fec3-428f-b6b1-f5850448b2ce?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/be05b43b-fec3-428f-b6b1-f5850448b2ce?feedback_type=other)</sup>&nbsp;&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[!
 [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]

Reply via email to