WSL: nvm: Node installation fails

Hi!

I’m trying to get multiple node versions running under bash on Windows. Installing nvm works fine, however trying to install any node versions errors out with:

tar: bin/npm: Cannot utime: Operation not permitted

To reproduce:

  1. Install nvm via curl script from creationix/nvm
  2. Try to install a node version nvm install 4

About this issue

  • Original URL
  • State: closed
  • Created 11 years ago
  • Reactions: 1
  • Comments: 20 (8 by maintainers)

Most upvoted comments

Looks like we’re getting past the tar error but I’m getting a different error ENOTTY error. We have a bunch of additional pts / tty support in the pipeline so we should try this again once that’s finished.

root@BENHILL-VM3:~# nvm install 4
Downloading https://nodejs.org/dist/v4.4.3/node-v4.4.3-linux-x64.tar.xz...
######################################################################## 100.0%
fs.js:549
  return binding.open(pathModule._makeLong(path), stringToFlags(flags), mode);
                 ^

Error: Unknown system error -25: Unknown system error -25, open '/root/.nvm/versions/node/v4.4.3/lib/node_modules/npm/bin/npm-cli.js'
    at Error (native)
    at Object.fs.openSync (fs.js:549:18)
    at Object.fs.readFileSync (fs.js:397:15)
    at Object.Module._extensions..js (module.js:415:20)
    at Module.load (module.js:343:32)
    at Function.Module._load (module.js:300:12)
    at Function.Module.runMain (module.js:441:10)
    at startup (node.js:139:18)
    at node.js:968:3
nvm is not compatible with the npm config "prefix" option: currently set to ""
Run `nvm use --delete-prefix v4.4.3` to unset it.

Fix is on the way. Just taking a little time to get on the insider fast ring. I have confirmed two versions of Node installed and managed through nvm on an internal build. Hopefully not much longer.

russ@RUSSALEX-BOOK:~$ nvm list -> v5.4.1 v6.0.0 default -> v6.0.0 node -> stable (-> v6.0.0) (default) stable -> 6.0 (-> v6.0.0) (default) iojs -> N/A (default) russ@RUSSALEX-BOOK:~$ node -v v5.4.1 russ@RUSSALEX-BOOK:~$ nvm use 6.0.0 Now using node v6.0.0 (npm v3.8.6) russ@RUSSALEX-BOOK:~$ node -v v6.0.0 russ@RUSSALEX-BOOK:~$

I dug into this issue today and I now have a fix in code review. With my fix I was able to use NVM to install nodejs 4 without issues.

I’ll give this a try on our internal build tomorrow. I’ve fixed some node issues recently so this may be fixed.

@benhillis Did this fix make it into build 14342? I’m still getting errors with last night’s update.