-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Description
Is there an existing issue for this?
- I have searched the existing issues
Description of the bug
goof docker build fails and the container is exited.
santa@roli:~$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
e7a8788d5e4d nodejs-goof_goof "npm start" 7 minutes ago Exited (9) 7 minutes ago goof
86ffaea201b0 mysql:5 "docker-entrypoint.s…" 7 minutes ago Up 7 minutes 0.0.0.0:3306->3306/tcp, 33060/tcp goof-mysql
b6ca72bb5cfe mongo "docker-entrypoint.s…" 7 minutes ago Up 7 minutes 0.0.0.0:27017->27017/tcp goof-mongo
santa@roli:~$ docker logs goof
[email protected] start /usr/src/goof
NODE_OPTIONS=--openssl-legacy-provider node app.js
node: --openssl-legacy-provider is not allowed in NODE_OPTIONS
npm ERR! code ELIFECYCLE
npm ERR! errno 9
npm ERR! [email protected] start: NODE_OPTIONS=--openssl-legacy-provider node app.js
npm ERR! Exit status 9
npm ERR!
npm ERR! Failed at the [email protected] start 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/2023-01-03T06_00_22_312Z-debug.log
santa@roli:~$ docker logs /root/.npm/_logs/2023-01-03T06_00_22_312Z-debug.log
Error: No such container: /root/.npm/_logs/2023-01-03T06_00_22_312Z-debug.log
Steps To Reproduce
git clone https://github.com/snyk-labs/nodejs-goof.git
cd nodejs-goof
docker-compose up --build
Additional Information
No response