olivia-ai/olivia

Installation/setup Front issues

maonguyen8x opened this issue · 5 comments

maonguyen8x commented

Hi, @hugolgst
Please check to help me the following errors:
First specify on which part this is related in the title with:
I tried to install the front in here: https://github.com/olivia-ai/olivia-ai.org

Describe the bug

I got an error starting front in olivia-ai.org with the docker :
➜ docker build -t front .
[+] Building 101.7s (9/11)
=> [internal] load build definition from Dockerfile 0.1s
=> => transferring dockerfile: 261B 0.0s
=> [internal] load .dockerignore 0.1s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/node:lts-alpine 3.2s
=> [1/7] FROM docker.io/library/node:lts-alpine@sha256:0a6a21d28509f56155007444075ef4fdd36eef0a97924623cb641d3766e3b8d3 0.0s
=> => resolve docker.io/library/node:lts-alpine@sha256:0a6a21d28509f56155007444075ef4fdd36eef0a97924623cb641d3766e3b8d3 0.0s
=> [internal] load build context 50.0s
=> => transferring context: 263.34MB 49.7s
=> CACHED [2/7] RUN npm install -g http-server 0.0s
=> CACHED [3/7] WORKDIR /app 0.0s
=> CACHED [4/7] COPY package*.json ./ 0.0s
=> ERROR [5/7] RUN npm ci 48.1s

[5/7] RUN npm ci:
#9 43.12
#9 43.12 > fsevents@1.2.9 install /app/node_modules/fsevents
#9 43.12 > node install
#9 43.12
#9 43.57
#9 43.57 > core-js@2.6.9 postinstall /app/node_modules/core-js
#9 43.57 > node scripts/postinstall || echo "ignore"
#9 43.57
#9 43.63 Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
#9 43.63
#9 43.63 The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
#9 43.63 > https://opencollective.com/core-js
#9 43.63 > https://www.patreon.com/zloirock
#9 43.63
#9 43.63 Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
#9 43.63
#9 44.13
#9 44.13 > node-sass@4.13.1 install /app/node_modules/node-sass
#9 44.13 > node scripts/install.js
#9 44.13
#9 45.08 Downloading binary from https://github.com/sass/node-sass/releases/download/v4.13.1/linux_musl-x64-83_binding.node
#9 45.70 Cannot download "https://github.com/sass/node-sass/releases/download/v4.13.1/linux_musl-x64-83_binding.node":
#9 45.70
#9 45.70 HTTP error 404 Not Found
#9 45.70
#9 45.70 Hint: If github.com is not accessible in your location
#9 45.70 try setting a proxy via HTTP_PROXY, e.g.
#9 45.70
#9 45.70 export HTTP_PROXY=http://example.com:1234
#9 45.70
#9 45.70 or configure npm proxy via
#9 45.70
#9 45.70 npm config set proxy http://example.com:8080
#9 45.71
#9 45.71 > node-sass@4.13.1 postinstall /app/node_modules/node-sass
#9 45.71 > node scripts/build.js
#9 45.71
#9 45.82 Building: /usr/local/bin/node /app/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
#9 45.93 gyp info it worked if it ends with ok
#9 45.93 gyp verb cli [
#9 45.93 gyp verb cli '/usr/local/bin/node',
#9 45.93 gyp verb cli '/app/node_modules/node-gyp/bin/node-gyp.js',
#9 45.93 gyp verb cli 'rebuild',
#9 45.93 gyp verb cli '--verbose',
#9 45.93 gyp verb cli '--libsass_ext=',
#9 45.93 gyp verb cli '--libsass_cflags=',
#9 45.94 gyp verb cli '--libsass_ldflags=',
#9 45.94 gyp verb cli '--libsass_library='
#9 45.94 gyp verb cli ]
#9 45.94 gyp info using node-gyp@3.8.0
#9 45.94 gyp info using node@14.16.0 | linux | x64
#9 45.94 gyp verb command rebuild []
#9 45.94 gyp verb command clean []
#9 45.95 gyp verb clean removing "build" directory
#9 45.96 gyp verb command configure []
#9 45.97 gyp verb check python checking for Python executable "python2" in the PATH
#9 45.98 gyp verb which failed Error: not found: python2
#9 45.98 gyp verb which failed at getNotFoundError (/app/node_modules/which/which.js:13:12)
#9 45.98 gyp verb which failed at F (/app/node_modules/which/which.js:68:19)
#9 45.98 gyp verb which failed at E (/app/node_modules/which/which.js:80:29)
#9 45.98 gyp verb which failed at /app/node_modules/which/which.js:89:16
#9 45.98 gyp verb which failed at /app/node_modules/isexe/index.js:42:5
#9 45.98 gyp verb which failed at /app/node_modules/isexe/mode.js:8:5
#9 45.98 gyp verb which failed at FSReqCallback.oncomplete (fs.js:183:21)
#9 45.98 gyp verb which failed python2 Error: not found: python2
#9 45.98 gyp verb which failed at getNotFoundError (/app/node_modules/which/which.js:13:12)
#9 45.98 gyp verb which failed at F (/app/node_modules/which/which.js:68:19)
#9 45.98 gyp verb which failed at E (/app/node_modules/which/which.js:80:29)
#9 45.98 gyp verb which failed at /app/node_modules/which/which.js:89:16
#9 45.98 gyp verb which failed at /app/node_modules/isexe/index.js:42:5
#9 45.98 gyp verb which failed at /app/node_modules/isexe/mode.js:8:5
#9 45.98 gyp verb which failed at FSReqCallback.oncomplete (fs.js:183:21) {
#9 45.98 gyp verb which failed code: 'ENOENT'
#9 45.98 gyp verb which failed }
#9 45.98 gyp verb check python checking for Python executable "python" in the PATH
#9 45.98 gyp verb which failed Error: not found: python
#9 45.98 gyp verb which failed at getNotFoundError (/app/node_modules/which/which.js:13:12)
#9 45.98 gyp verb which failed at F (/app/node_modules/which/which.js:68:19)
#9 45.99 gyp verb which failed at E (/app/node_modules/which/which.js:80:29)
#9 45.99 gyp verb which failed at /app/node_modules/which/which.js:89:16
#9 45.99 gyp verb which failed at /app/node_modules/isexe/index.js:42:5
#9 45.99 gyp verb which failed at /app/node_modules/isexe/mode.js:8:5
#9 45.99 gyp verb which failed at FSReqCallback.oncomplete (fs.js:183:21)
#9 45.99 gyp verb which failed python Error: not found: python
#9 45.99 gyp verb which failed at getNotFoundError (/app/node_modules/which/which.js:13:12)
#9 45.99 gyp verb which failed at F (/app/node_modules/which/which.js:68:19)
#9 45.99 gyp verb which failed at E (/app/node_modules/which/which.js:80:29)
#9 45.99 gyp verb which failed at /app/node_modules/which/which.js:89:16
#9 45.99 gyp verb which failed at /app/node_modules/isexe/index.js:42:5
#9 45.99 gyp verb which failed at /app/node_modules/isexe/mode.js:8:5
#9 45.99 gyp verb which failed at FSReqCallback.oncomplete (fs.js:183:21) {
#9 45.99 gyp verb which failed code: 'ENOENT'
#9 45.99 gyp verb which failed }
#9 45.99 gyp ERR! configure error
#9 45.99 gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
#9 45.99 gyp ERR! stack at PythonFinder.failNoPython (/app/node_modules/node-gyp/lib/configure.js:484:19)
#9 45.99 gyp ERR! stack at PythonFinder. (/app/node_modules/node-gyp/lib/configure.js:406:16)
#9 45.99 gyp ERR! stack at F (/app/node_modules/which/which.js:68:16)
#9 45.99 gyp ERR! stack at E (/app/node_modules/which/which.js:80:29)
#9 45.99 gyp ERR! stack at /app/node_modules/which/which.js:89:16
#9 45.99 gyp ERR! stack at /app/node_modules/isexe/index.js:42:5
#9 45.99 gyp ERR! stack at /app/node_modules/isexe/mode.js:8:5
#9 45.99 gyp ERR! stack at FSReqCallback.oncomplete (fs.js:183:21)
#9 45.99 gyp ERR! System Linux 4.19.128-microsoft-standard
#9 45.99 gyp ERR! command "/usr/local/bin/node" "/app/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_
library="
#9 45.99 gyp ERR! cwd /app/node_modules/node-sass
#9 45.99 gyp ERR! node -v v14.16.0
#9 46.00 gyp ERR! node-gyp -v v3.8.0
#9 46.00 gyp ERR! not ok
#9 46.00 Build failed with error code: 1
#9 46.01 npm ERR! code ELIFECYCLE
#9 46.01 npm ERR! errno 1
#9 46.02 npm ERR! node-sass@4.13.1 postinstall: node scripts/build.js
#9 46.02 npm ERR! Exit status 1
#9 46.02 npm ERR!
#9 46.02 npm ERR! Failed at the node-sass@4.13.1 postinstall script.
#9 46.03 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
#9 46.11
#9 46.11 npm ERR! A complete log of this run can be found in:
#9 46.11 npm ERR! /root/.npm/_logs/2021-04-02T05_52_24_775Z-debug.log

executor failed running [/bin/sh -c npm ci]: exit code: 1

To Reproduce
Follow the installation instructions in the readme.

  1. docker build -t front .
  2. docker run -p 8080:8080 front

Expected behavior
For it to start the frontend as https://github.com/olivia-ai/olivia-ai.org.

Desktop (please complete the following information):

  • Goland IDE Tool

Additional context
Console print below.
➜ docker build -t front .
[+] Building 101.7s (9/11)
=> [internal] load build definition from Dockerfile 0.1s
=> => transferring dockerfile: 261B 0.0s
=> [internal] load .dockerignore 0.1s
=> => transferring context: 2B 0.0s
=> [internal] load metadata for docker.io/library/node:lts-alpine 3.2s
=> [1/7] FROM docker.io/library/node:lts-alpine@sha256:0a6a21d28509f56155007444075ef4fdd36eef0a97924623cb641d3766e3b8d3 0.0s
=> => resolve docker.io/library/node:lts-alpine@sha256:0a6a21d28509f56155007444075ef4fdd36eef0a97924623cb641d3766e3b8d3 0.0s
=> [internal] load build context 50.0s
=> => transferring context: 263.34MB 49.7s
=> CACHED [2/7] RUN npm install -g http-server 0.0s
=> CACHED [3/7] WORKDIR /app 0.0s
=> CACHED [4/7] COPY package*.json ./ 0.0s
=> ERROR [5/7] RUN npm ci 48.1s

[5/7] RUN npm ci:
#9 43.12
#9 43.12 > fsevents@1.2.9 install /app/node_modules/fsevents
#9 43.12 > node install
#9 43.12
#9 43.57
#9 43.57 > core-js@2.6.9 postinstall /app/node_modules/core-js
#9 43.57 > node scripts/postinstall || echo "ignore"
#9 43.57
#9 43.63 Thank you for using core-js ( https://github.com/zloirock/core-js ) for polyfilling JavaScript standard library!
#9 43.63
#9 43.63 The project needs your help! Please consider supporting of core-js on Open Collective or Patreon:
#9 43.63 > https://opencollective.com/core-js
#9 43.63 > https://www.patreon.com/zloirock
#9 43.63
#9 43.63 Also, the author of core-js ( https://github.com/zloirock ) is looking for a good job -)
#9 43.63
#9 44.13
#9 44.13 > node-sass@4.13.1 install /app/node_modules/node-sass
#9 44.13 > node scripts/install.js
#9 44.13
#9 45.08 Downloading binary from https://github.com/sass/node-sass/releases/download/v4.13.1/linux_musl-x64-83_binding.node
#9 45.70 Cannot download "https://github.com/sass/node-sass/releases/download/v4.13.1/linux_musl-x64-83_binding.node":
#9 45.70
#9 45.70 HTTP error 404 Not Found
#9 45.70
#9 45.70 Hint: If github.com is not accessible in your location
#9 45.70 try setting a proxy via HTTP_PROXY, e.g.
#9 45.70
#9 45.70 export HTTP_PROXY=http://example.com:1234
#9 45.70
#9 45.70 or configure npm proxy via
#9 45.70
#9 45.70 npm config set proxy http://example.com:8080
#9 45.71
#9 45.71 > node-sass@4.13.1 postinstall /app/node_modules/node-sass
#9 45.71 > node scripts/build.js
#9 45.71
#9 45.82 Building: /usr/local/bin/node /app/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
#9 45.93 gyp info it worked if it ends with ok
#9 45.93 gyp verb cli [
#9 45.93 gyp verb cli '/usr/local/bin/node',
#9 45.93 gyp verb cli '/app/node_modules/node-gyp/bin/node-gyp.js',
#9 45.93 gyp verb cli 'rebuild',
#9 45.93 gyp verb cli '--verbose',
#9 45.93 gyp verb cli '--libsass_ext=',
#9 45.93 gyp verb cli '--libsass_cflags=',
#9 45.94 gyp verb cli '--libsass_ldflags=',
#9 45.94 gyp verb cli '--libsass_library='
#9 45.94 gyp verb cli ]
#9 45.94 gyp info using node-gyp@3.8.0
#9 45.94 gyp info using node@14.16.0 | linux | x64
#9 45.94 gyp verb command rebuild []
#9 45.94 gyp verb command clean []
#9 45.95 gyp verb clean removing "build" directory
#9 45.96 gyp verb command configure []
#9 45.97 gyp verb check python checking for Python executable "python2" in the PATH
#9 45.98 gyp verb which failed Error: not found: python2
#9 45.98 gyp verb which failed at getNotFoundError (/app/node_modules/which/which.js:13:12)
#9 45.98 gyp verb which failed at F (/app/node_modules/which/which.js:68:19)
#9 45.98 gyp verb which failed at E (/app/node_modules/which/which.js:80:29)
#9 45.98 gyp verb which failed at /app/node_modules/which/which.js:89:16
#9 45.98 gyp verb which failed at /app/node_modules/isexe/index.js:42:5
#9 45.98 gyp verb which failed at /app/node_modules/isexe/mode.js:8:5
#9 45.98 gyp verb which failed at FSReqCallback.oncomplete (fs.js:183:21)
#9 45.98 gyp verb which failed python2 Error: not found: python2
#9 45.98 gyp verb which failed at getNotFoundError (/app/node_modules/which/which.js:13:12)
#9 45.98 gyp verb which failed at F (/app/node_modules/which/which.js:68:19)
#9 45.98 gyp verb which failed at E (/app/node_modules/which/which.js:80:29)
#9 45.98 gyp verb which failed at /app/node_modules/which/which.js:89:16
#9 45.98 gyp verb which failed at /app/node_modules/isexe/index.js:42:5
#9 45.98 gyp verb which failed at /app/node_modules/isexe/mode.js:8:5
#9 45.98 gyp verb which failed at FSReqCallback.oncomplete (fs.js:183:21) {
#9 45.98 gyp verb which failed code: 'ENOENT'
#9 45.98 gyp verb which failed }
#9 45.98 gyp verb check python checking for Python executable "python" in the PATH
#9 45.98 gyp verb which failed Error: not found: python
#9 45.98 gyp verb which failed at getNotFoundError (/app/node_modules/which/which.js:13:12)
#9 45.98 gyp verb which failed at F (/app/node_modules/which/which.js:68:19)
#9 45.99 gyp verb which failed at E (/app/node_modules/which/which.js:80:29)
#9 45.99 gyp verb which failed at /app/node_modules/which/which.js:89:16
#9 45.99 gyp verb which failed at /app/node_modules/isexe/index.js:42:5
#9 45.99 gyp verb which failed at /app/node_modules/isexe/mode.js:8:5
#9 45.99 gyp verb which failed at FSReqCallback.oncomplete (fs.js:183:21)
#9 45.99 gyp verb which failed python Error: not found: python
#9 45.99 gyp verb which failed at getNotFoundError (/app/node_modules/which/which.js:13:12)
#9 45.99 gyp verb which failed at F (/app/node_modules/which/which.js:68:19)
#9 45.99 gyp verb which failed at E (/app/node_modules/which/which.js:80:29)
#9 45.99 gyp verb which failed at /app/node_modules/which/which.js:89:16
#9 45.99 gyp verb which failed at /app/node_modules/isexe/index.js:42:5
#9 45.99 gyp verb which failed at /app/node_modules/isexe/mode.js:8:5
#9 45.99 gyp verb which failed at FSReqCallback.oncomplete (fs.js:183:21) {
#9 45.99 gyp verb which failed code: 'ENOENT'
#9 45.99 gyp verb which failed }
#9 45.99 gyp ERR! configure error
#9 45.99 gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
#9 45.99 gyp ERR! stack at PythonFinder.failNoPython (/app/node_modules/node-gyp/lib/configure.js:484:19)
#9 45.99 gyp ERR! stack at PythonFinder. (/app/node_modules/node-gyp/lib/configure.js:406:16)
#9 45.99 gyp ERR! stack at F (/app/node_modules/which/which.js:68:16)
#9 45.99 gyp ERR! stack at E (/app/node_modules/which/which.js:80:29)
#9 45.99 gyp ERR! stack at /app/node_modules/which/which.js:89:16
#9 45.99 gyp ERR! stack at /app/node_modules/isexe/index.js:42:5
#9 45.99 gyp ERR! stack at /app/node_modules/isexe/mode.js:8:5
#9 45.99 gyp ERR! stack at FSReqCallback.oncomplete (fs.js:183:21)
#9 45.99 gyp ERR! System Linux 4.19.128-microsoft-standard
#9 45.99 gyp ERR! command "/usr/local/bin/node" "/app/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_
library="
#9 45.99 gyp ERR! cwd /app/node_modules/node-sass
#9 45.99 gyp ERR! node -v v14.16.0
#9 46.00 gyp ERR! node-gyp -v v3.8.0
#9 46.00 gyp ERR! not ok
#9 46.00 Build failed with error code: 1
#9 46.01 npm ERR! code ELIFECYCLE
#9 46.01 npm ERR! errno 1
#9 46.02 npm ERR! node-sass@4.13.1 postinstall: node scripts/build.js
#9 46.02 npm ERR! Exit status 1
#9 46.02 npm ERR!
#9 46.02 npm ERR! Failed at the node-sass@4.13.1 postinstall script.
#9 46.03 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
#9 46.11
#9 46.11 npm ERR! A complete log of this run can be found in:
#9 46.11 npm ERR! /root/.npm/_logs/2021-04-02T05_52_24_775Z-debug.log

executor failed running [/bin/sh -c npm ci]: exit code: 1

Thank you.

A-Yamout commented

This sounds like a npm problem because it can't find the "https://github.com/sass/node-sass/releases/download/v4.13.1/linux_musl-x64-83_binding.node" I would start an issue with npm. Otherwise, I don't know any other way to fix it.

josecelano commented

I had the same problem and I fixed updating node-saas version: olivia-ai/olivia-ai.org#200 for the frontend app. I could also run the application using the production websocket: wss://olivia-api.herokuapp.com/websocketbut I suppose I could also run it locally.

hugolgst commented

In any case I am working on a re-build of most of the communication between the Front-end and the Back-end to simplify all that.
It will be a huge work and take a lot of time but hopefully it stays on tracks

hugolgst commented

It might fix a lot of the deployment issues we have.

hugolgst commented

Closing because it is going to be solved with v3