Hi!! version 6.0.0 release great thankyou
execute docker-compose up command is fails
error message
> [email protected] bundle /app
> bin/bundle-extensions
> [email protected] build /app
> npm run clean && NODE_ENV=production node --max-old-space-size=4096 node_modules/.bin/webpack
> [email protected] clean /app
> rm -rf ./client/dist/
Killed
npm ERR! Linux 4.9.125-linuxkit
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run" "build"
npm ERR! node v6.11.0
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] build: `npm run clean && NODE_ENV=production node --max-old-space-size=4096 node_modules/.bin/webpack`
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the [email protected] build script 'npm run clean && NODE_ENV=production node --max-old-space-size=4096 node_modules/.bin/webpack'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the redash-client package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! npm run clean && NODE_ENV=production node --max-old-space-size=4096 node_modules/.bin/webpack
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs redash-client
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls redash-client
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /app/npm-debug.log
ERROR: Service 'server' failed to build: The command '/bin/sh -c npm install && npm run bundle && npm run build && rm -rf node_modules' returned a non-zero code: 1
Mismatch between the node version of the redash/base docker image and the version in the package.json.
I think that the node version of the redash/base docker image need to be updated.
in docker redash/base image node version : v6.11.0
in package.json node version :
"engines": {
"node": "^8.0.0",
....
Good catch. I'm surprised this doesn't happen on CI 馃
Looking at the output again, I think it fails not because of the Node version but because it runs out of memory. Make sure that you assigned enough memory to the Docker VM (if you're using Docker Mac, you can change this from their UI).
We had to update the amount of memory webpack is using during the build. We hope to reduce it when we remove Angular's dependencies.
Thank you!!
Memory allocation to Docker VM was 2 GB
Increase allocated memory and try again:bow:
@arikfr
I increased memory allocation and succeeded in booting
Thank you
Most helpful comment
Looking at the output again, I think it fails not because of the Node version but because it runs out of memory. Make sure that you assigned enough memory to the Docker VM (if you're using Docker Mac, you can change this from their UI).
We had to update the amount of memory webpack is using during the build. We hope to reduce it when we remove Angular's dependencies.