keehl1213 commented on issue #8818: URL: https://github.com/apache/incubator-superset/issues/8818#issuecomment-731884959
> Upon further inspection, I noticed that the `superset_node` container died. Here is the tail of the logs for it: > > ``` > <s> [webpack.Progress] 94% after asset optimization > <s> [webpack.Progress] 94% after seal > <s> [webpack.Progress] 95% emitting > <s> [webpack.Progress] 95% emitting fork-ts-checker-webpack-plugin > <s> [webpack.Progress] 95% emitting clean-webpack-plugin > <s> [webpack.Progress] 95% emitting ManifestPlugin > Killed > npm ERR! code ELIFECYCLE > npm ERR! errno 137 > npm ERR! [email protected] dev: `webpack --mode=development --colors --debug --watch` > npm ERR! Exit status 137 > npm ERR! > npm ERR! Failed at the [email protected] dev 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! /root/.npm/_logs/2020-11-21T22_04_07_103Z-debug.log > npm WARN using --force I sure hope you know what you are doing. > /usr/local/bin/webpack -> /usr/local/lib/node_modules/webpack/bin/webpack.js > /usr/local/bin/webpack-cli -> /usr/local/lib/node_modules/webpack-cli/bin/cli.js > + [email protected] > + [email protected] > updated 2 packages in 7.314s > npm WARN using --force I sure hope you know what you are doing. > ``` Status 137 is out of memory. Maybe 4 GB of RAM is not enough. My docker has 5 GB of memory and 3 GB of swap on windows 10. It works fine for me. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
