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

   <!-- Answer -->
   I found a similar closed issue, [docker build 
failed](https://github.com/apache/superset/issues/22429), which was last 
updated on December 21, 2022. The suggested solution was to ensure that the 
`zstd` package is installed in the Dockerfile. Here’s how you can resolve the 
"zstd not found" error:
   
   1. **Ensure `zstd` is installed in the Dockerfile**:
      The Dockerfile should include the installation of `zstd`:
   
      ```dockerfile
      # Somehow we need python3 + build-essential on this side of the house to 
install node-gyp
      RUN apt-get update -qq \
          && apt-get install \
              -yqq --no-install-recommends \
              build-essential \
              python3 \
              zstd
      ```
   
   2. **Rebuild the Docker image without using the cache**:
      If you are still encountering the error, it might be due to a caching 
issue or an incomplete build. Try rebuilding the Docker image without using the 
cache:
   
      ```sh
      docker compose build --no-cache
      docker compose up
      ```
   
   3. **Ensure `simple-zstd` is included in `package.json`**:
      Make sure that the `simple-zstd` package is included in your 
`package.json` and properly installed, as it is required by 
`webpack.proxy-config.js` for handling `zstd` compression:
   
      ```json
      "dependencies": {
        "simple-zstd": "^1.0.0"
      }
      ```
   
      Run the following command to install the necessary npm packages:
   
      ```sh
      npm install
      ```
   
   This should help resolve the error you are encountering 
<sup>[[1]](https://github.com/apache/superset/issues/22429)</sup><sup>[[2]](https://github.com/apache/superset/blob/master/Dockerfile)</sup>.
   
   
   <!-- Dosu Comment Footer -->
   *To continue talking to [Dosu](https://dosu.dev), mention @dosu.*
   


-- 
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