Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't run the web server #741

Closed
lvlrSajjad opened this issue May 3, 2021 · 1 comment
Closed

Can't run the web server #741

lvlrSajjad opened this issue May 3, 2021 · 1 comment

Comments

@lvlrSajjad
Copy link

lvlrSajjad commented May 3, 2021

After running this command:

hollaex web --setup

I encounter the error below:

Error
[+] Building 232.3s (15/19)                                                     
 => [internal] load build definition from Dockerfile                       0.0s
 => => transferring dockerfile: 127B                                       0.0s
 => [internal] load .dockerignore                                          0.0s
 => => transferring context: 2B                                            0.0s
 => [internal] load metadata for docker.io/library/nginx:1.16.0-alpine     6.7s
 => [internal] load metadata for docker.io/library/node:12.18.3-alpine     6.0s
 => [auth] library/nginx:pull token for registry-1.docker.io               0.0s
 => [auth] library/node:pull token for registry-1.docker.io                0.0s
 => [internal] load build context                                          0.2s
 => => transferring context: 90.63kB                                       0.2s
 => [build 1/6] FROM docker.io/library/node:12.18.3-alpine@sha256:c8efbb3  0.0s
 => [stage-1 1/6] FROM docker.io/library/nginx:1.16.0-alpine@sha256:270be  0.0s
 => CACHED [stage-1 2/6] RUN apk add --update     curl     && rm -rf /var  0.0s
 => CACHED [build 2/6] WORKDIR /app                                        0.0s
 => CACHED [build 3/6] COPY package.json /app/package.json                 0.0s
 => CACHED [build 4/6] RUN npm install --loglevel=error                    0.0s
 => CACHED [build 5/6] COPY . /app                                         0.0s
 => ERROR [build 6/6] RUN npm run build                                  225.3s
------                                                                          
 > [build 6/6] RUN npm run build:                                               
#15 0.838                                                                       
#15 0.838 > hollaex-kit@2.1.1 build /app                                        
#15 0.838 > npm run build-css && react-scripts --max_old_space_size=2048 build
#15 0.838 
#15 1.148 
#15 1.148 > hollaex-kit@2.1.1 build-css /app
#15 1.148 > node-sass-chokidar src/ -o src/
#15 1.148 
#15 2.127 Rendering Complete, saving .css file...
#15 2.132 Wrote CSS to /app/src/index.css
#15 2.133 Wrote 1 CSS files to /app/src/
#15 4.638 Creating an optimized production build...
#15 224.8 The build failed because the process exited too early. This probably means the system ran out of memory or someone called `kill -9` on the process.
#15 225.1 npm ERR! code ELIFECYCLE
#15 225.1 npm ERR! errno 1
#15 225.1 npm ERR! hollaex-kit@2.1.1 build: `npm run build-css && react-scripts --max_old_space_size=2048 build`
#15 225.1 npm ERR! Exit status 1
#15 225.1 npm ERR! 
#15 225.1 npm ERR! Failed at the hollaex-kit@2.1.1 build script.
#15 225.1 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
#15 225.2 
#15 225.2 npm ERR! A complete log of this run can be found in:
#15 225.2 npm ERR!     /root/.npm/_logs/2021-05-03T18_29_11_324Z-debug.log
------
executor failed running [/bin/sh -c npm run build]: exit code: 1
Failed to build the image.
Please confirm your configurations and try again.
If you are not on a latest HollaEx Kit, Please update it first to latest.

I changed --max_old_space_size=2048 multiple times afterwards but still it says:

#15 224.8 The build failed because the process exited too early. This probably means the system ran out of memory or someone called `kill -9` on the process.

Any Idea?
I'm running it on MacBook pro

@lvlrSajjad
Copy link
Author

Ok Just fixed it by adjusting the maximum memory in the docker preferences.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant