Incubator-superset: Problem installing Superset via Docker

[ivansocket]

Following 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! [email protected] 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 [email protected] 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-label-bot[bot]]

Issue-Label Bot is automatically applying the label #bug to this issue, with a confidence of 0.75. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

[mmantel]

I had this same problem and was able to get past it after increasing the resources in my Docker preferences (from 2.0 GiB to 4.0GiB of memory and 1.0 GiB to 2.0 GiB of swap).

[domehead100]

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.

[micimize]

Same applied with docker for mac - 2 -> 5GB memory and 1 -> 2GB swap worked for me.
92% chunk asset optimization TerserPlugin is where my build hung.

[moonrinnn]

What is node's version do we need to use?

[schrepfler]

Still an issue with latest from master (docker allocation 10GB memory, 2GB swap). Running on Docker for Mac. Happens even outside of container if I run npm ci && npm run build && rm -rf node_modules

[barmic12]

Increasing swap to 2GB and memory to 4GB (for Docker) resolved problem on my Mac.

[bharath0208]

The same thing worked for me

[cfmeyers]

Increasing the swap/memory did work for me (2GB swap, 4GB memory). It did pause for 3-5 minutes on that same 92% chunk asset optimization TerserPlugin, but it moved past that step and finish successfully.

[dpgaspar]

Thank you everyone for your help here. @ivansocket going to close this, feel free to reopen if the memory increase did not solved the issue