zstd not found by superset_node during docker compose up dev mode about superset HOT 4 OPEN

I found a similar closed issue, docker build failed, 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:

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

   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:

   "dependencies": {
     "simple-zstd": "^1.0.0"
   }

   Run the following command to install the necessary npm packages:

   npm install

This should help resolve the error you are encountering ^[1][2].

To continue talking to Dosu, mention @dosu.

from superset.

I hit this error too, on macos arm64 .

superset_node         | > webpack --mode=development --color --watch
superset_node         | 
superset_node         | [webpack-cli] Failed to load '/app/superset-frontend/webpack.config.js' config
superset_node         | [webpack-cli] Error: Can not access zstd! Is it installed?

from superset.

Same here, anyone found how to workaround this issue?

from superset.

Same here, anyone found how to workaround this issue?

If you read the PR linked in the description there’s a hacky solution to get things moving.

from superset.