jitsi / moderated-meetings

Jitsi Moderated Meetings microservice
Apache License 2.0
22 stars 14 forks source link

Docker build fails #31

Open luebke-dev opened 1 year ago

luebke-dev commented 1 year ago

Hey, its currently impossible to build the docker image because node_modules/.staging is missing. Any idea how to fix that?

[INFO] Replacing main artifact with repackaged archive
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  20.331 s
[INFO] Finished at: 2023-06-20T12:08:04Z
[INFO] ------------------------------------------------------------------------
INFO[0104] Taking snapshot of full filesystem...        
INFO[0108] RUN npm install && npm run build             
INFO[0108] Cmd: /bin/sh                                 
INFO[0108] Args: [-c npm install && npm run build]      
INFO[0108] Running: [/bin/sh -c npm install && npm run build] 
npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but package-lock.json was generated for lockfileVersion@2. I'll try to do my best with it!
npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/util-deprecate-ae90584c/package.json'
npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/util-deprecate-ae90584c/README.md'
npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/util-deprecate-ae90584c/LICENSE'
npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/util-deprecate-ae90584c/browser.js'
npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/util-deprecate-ae90584c/node.js'
npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/util-deprecate-ae90584c/History.md'
npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno -2
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t ssh://git@github.com/jitsi/jitsi-meet-logger.git
npm ERR! enoent 
npm ERR! enoent 
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-06-20T12_08_15_056Z-debug.log
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 254
section_end:1687262895:step_script
section_start:1687262895:cleanup_file_variables
Cleaning up project directory and file based variables
section_end:1687262895:cleanup_file_variables
ERROR: Job failed: exit code 254

damencho commented 1 year ago

Which npm version is this using?

luebke-dev commented 1 year ago

On my local machine 8.19.4 but it fails with the same error while building the docker container.

damencho commented 1 year ago

Does it works for you if you apply https://github.com/jitsi/moderated-meetings/pull/32?

luebke-dev commented 1 year ago

still gives me the same errors:

#0 4.141 npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/ajv-cfb765f1/dist/ajv.min.js.map'
#0 4.149 npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/react-dom-1e3d80c2/umd/react-dom.profiling.min.js'
#0 4.150 npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/tsutils-cf4512e3/typeguard/next/type.js'
#0 4.151 npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/json5-f18e2a85/lib/index.js'
#0 4.154 npm WARN tar ENOENT: no such file or directory, lstat '/opt/moderated-meetings/node_modules/.staging/ajv-cfb765f1/lib'
#0 4.155 npm WARN tar ENOENT: no such file or directory, open '/opt/moderated-meetings/node_modules/.staging/json5-f18e2a85/dist/index.min.js'
damencho commented 1 year ago

This is warn and should not stop the whole thing, although I do not see those errors locally. Do you have it if you delete node_modules and start with npm install? You are not executing this as a root, right?