pa-mike commented on issue #17076: URL: https://github.com/apache/superset/issues/17076#issuecomment-1034272450
> Docker didn't work for me, I checked out the `docker/docker-frontend.sh` script, and ran those commands manually. i.e.: > > ``` > # get nodejs from conda-forge in my case > conda install -c conda-forge nodejs > cd superset-frontend > npm install -f --no-optional --global webpack webpack-cli > npm install -f --no-optional > npm run dev > ``` > > My guess is some of the init scripts should have run this, but because nodejs is not installed it skipped it. I guess the installation docs can be improved on this. I had this same issue, running those node items solved my lockup on docker-compose. Looks like non-dev works fine, but the dev docker-compose has this challenge. > This is the kind of problem that discourages a lot of people who are having their first contact with the project following the tutorial. I would like to fix it, is anyone already working on it? Any suggestion on the best approach? Agree this issue is a bit discouraging, requires getting your hands dirty. -- 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]
