Freddy Taborda
PreguntaBuenas tardes.
No comprendo este error.
tep 4/6 : RUN npm install
—> Running in dbeea8950cd5
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/signal-exit-03ea760a/package.json’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/signal-exit-03ea760a/README.md’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/signal-exit-03ea760a/index.js’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/signal-exit-03ea760a/signals.js’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/signal-exit-03ea760a/CHANGELOG.md’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/saslprep-19c830a5/generate-code-points.js’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/signal-exit-03ea760a/LICENSE.txt’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/saslprep-19c830a5/index.js’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/saslprep-19c830a5/LICENSE’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/saslprep-19c830a5/readme.md’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/diff-0adba1be/dist/diff.min.js’
npm WARN tar ENOENT: no such file or directory, open '/usr/src/node_modules/.staging/source-map-9e04142d/dist/source-map.js’
npm ERR! code E404
npm ERR! 404 Not Found: event-stream@3.3.6
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-03-21T20_10_17_342Z-debug.log
Muchas gracias por sus comentarios
Guido Vilariño
esto es un error de
npmdockerFreddy Taborda
Muchas gracias por responder. $ git clone https://github.com/platzi/docker $ cd docker/ $ docker build -t platziapp .
He probado con Linux Mint Stable y Kali Linux stable. Si requieres algo mas de información por favor me indicas.
De nuevo muchas gracias por responder.
Saludos
Guido Vilariño
Acabo de pushear un fix en el
package-lock.json
