Problem installing Superset via Docker
See original GitHub issueFollowing the “Start with Docker” instructions from: https://superset.incubator.apache.org/installation.html
When executing the following command: https://superset.incubator.apache.org/installation.html
I get the warning: (node:6) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 SIGINT listeners added. Use emitter.setMaxListeners() to increase limit in red color and then:
clean-webpack-plugin: /home/superset/superset/assets/dist has been removed.
Starting type checking service…
Using 1 worker with 2048MB memory limit
92% chunk asset optimization TerserPluginnpm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! superset@0.999.0-dev build: cross-env NODE_OPTIONS=--max_old_space_size=8192 NODE_ENV=production webpack --mode=production --colors --progress
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the superset@0.999.0-dev build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in: npm ERR! /home/superset/.npm/_logs/2019-09-10T16_43_28_302Z-debug.log ERROR: Service ‘superset’ failed to build: The command ‘/bin/sh -c cd superset/assets && npm ci && npm run build && rm -rf node_modules’ returned a non-zero code: 1
Afther this the instalation stops. I don’t understand what do I need to do in order for Superset to install normally.
Thanks in advance.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:11 (2 by maintainers)
Top GitHub Comments
Just ran into this trying to run superset in docker (Docker Desktop for Windows with Linux containers). Docker has 8GB of memory and 1GB of swap.
Seems this might be related to https://github.com/webpack-contrib/uglifyjs-webpack-plugin/issues/272, though that issue is related to Uglify is closed and they seem to think it is fixed in the Terser plugin, but it seems it might not be entirely fixed.
I did increase the swap from 1GB to 2GB, and then it built okay on the second attempt.
Issue-Label Bot is automatically applying the label
#bug
to this issue, with a confidence of 0.75. Please mark this comment with 👍 or 👎 to give our bot feedback!Links: app homepage, dashboard and code for this bot.