You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Removing intermediate container 8cb49e6250b7
Step 51/65 : RUN npm install -g .
---> Running in c565791d1a88
npm WARN prepublish-on-install As of npm@5, `prepublish` scripts will run only for `npm publish`.
npm WARN prepublish-on-install (In npm@4 and previous versions, it also runs for `npm install`.)
npm WARN prepublish-on-install See the deprecation note in `npm help scripts` for more information.
npm WARN lifecycle ethereumjs-testrpc@6.0.1~prepublish: cannot run in wd %s %s (wd=%s) ethereumjs-testrpc@6.0.1 npm run build /tmp/testrpc
/usr/lib
`-- (empty)
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/ethereumjs-testrpc/node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! Linux 3.13.0-117-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "."
npm ERR! node v7.10.1
npm ERR! npm v4.2.0
npm ERR! path /usr/lib/node_modules/ethereumjs-testrpc/build/cli.node.js
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/lib/node_modules/ethereumjs-testrpc/build/cli.node.js'
npm ERR! enoent ENOENT: no such file or directory, chmod '/usr/lib/node_modules/ethereumjs-testrpc/build/cli.node.js'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! Please include the following file with any support request:
npm ERR! /root/.npm/_logs/2017-11-03T10_29_36_463Z-debug.log
The command '/bin/sh -c npm install -g .' returned a non-zero code: 1
The text was updated successfully, but these errors were encountered:
The text was updated successfully, but these errors were encountered: