Unable to install `acorn` npm package (inability to symlink on mounted drives) #3

EvHaus · 2016-04-07T01:50:10Z

Steps to reproduce:

Launch "Bash on Ubuntu on Windows" (note that it appears to use the 'root' user by default)
Install nodejs via: curl -sL https://deb.nodesource.com/setup_5.x | sudo -E bash -
sudo apt-get install -y nodejs
Try to install the acorn package via npm install acorn

You'll get this message:

npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "acorn"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! path ../acorn/bin/acorn
npm ERR! code EPERM
npm ERR! errno -1
npm ERR! syscall symlink

npm ERR! Error: EPERM: operation not permitted, symlink '../acorn/bin/acorn' -> '/mnt/r/path/node_modules/.bin/acorn'
npm ERR!     at Error (native)
npm ERR!  { [Error: EPERM: operation not permitted, symlink '../acorn/bin/acorn' -> '/mnt/r/path/node_modules/.bin/acorn']
npm ERR!   errno: -1,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'symlink',
npm ERR!   path: '../acorn/bin/acorn',
npm ERR!   dest: '/mnt/r/path/node_modules/.bin/acorn',
npm ERR!   parent: 'myproject' }
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     /mnt/r/path/npm-debug.log

Not sure how to proceed as I'm already root with full permissions

UPDATE: For other nodejs developers finding this issue. Here is what I seem to have uncovered so far:

npm install -g {anything} doesn't seem to work
npm install {anything} doesn't seem to work if installing anywhere on /
npm install {some_packages} on /mnt/{something} sometimes doesn't work depending on whether or not that package needs to create symlinks

The text was updated successfully, but these errors were encountered:

mike-morr · 2016-04-07T01:56:11Z

Did you run the bash window as administrator in Windows? My very limited understanding is that in order for you to actually have elevated permissions to the underlying file system (and probably other stuff) you need to open the window elevated.

EvHaus · 2016-04-07T02:12:33Z

Launching "Bash on Ubuntu on Windows" with "Run as administrator" did not help resolve this issue. The same error appears.

EvHaus · 2016-04-07T02:15:23Z

It appears, ln -s doesn't work on the mounted drives, which is what's causing the issue:

cd /mnt/c/Windows/Temp
touch a
ln -s a b
> ln: failed to create symbolic link ‘b’: Operation not permitted

russalex · 2016-04-07T02:18:01Z

Before going into possible solutions, I should point out that there are some issues with npm not related to symlinks. I have not tried acorn but will make certain this is one of our test.

I should also point out that we have added a little bit about the filesystem here: https://msdn.microsoft.com/en-us/commandline/wsl/faq.

That said, are you able to install acorn someplace under '/'?

EvHaus · 2016-04-07T02:20:02Z

That said, are you able to install acorn someplace under '/'?

No. This works:

cd /tmp
touch a
ln -s a b

But this doesn't:

root@localhost:/tmp# npm install acorn
npm WARN enoent ENOENT: no such file or directory, open '/tmp/package.json'
npm WARN tmp No description
npm WARN tmp No repository field.
npm WARN tmp No README data
npm WARN tmp No license field.
npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "acorn"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! path /tmp/node_modules/.staging/acorn-baee3507
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall rename

npm ERR! Error: EACCES: permission denied, rename '/tmp/node_modules/.staging/acorn-baee3507' -> '/tmp/node_modules/acorn'
npm ERR!     at destStatted (/usr/lib/node_modules/npm/lib/install/action/finalize.js:25:7)
npm ERR!     at FSReqWrap.oncomplete (fs.js:82:15)
npm ERR!
npm ERR! Error: EACCES: permission denied, rename '/tmp/node_modules/.staging/acorn-baee3507' -> '/tmp/node_modules/acorn'
npm ERR!     at Error (native)
npm ERR!  [Error: EACCES: permission denied, rename '/tmp/node_modules/.staging/acorn-baee3507' -> '/tmp/node_modules/acorn']
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     /tmp/npm-debug.log

EDIT: But I'm actually unable to install anything in /. All npm packages seem to give that same error message. Tried in /tmp as well as /home.

Furthermore, trying to install a package globally returns an entirely new error:

root@localhost:/home# npm install -g acorn
Error: could not get uid/gid
net.js:135
    this._handle.open(options.fd);
                 ^

Error: EINVAL: invalid argument, uv_pipe_open
    at Error (native)
    at new Socket (net.js:135:18)
    at createWritableStdioStream (internal/process/stdio.js:142:16)
    at process.stdout (internal/process/stdio.js:10:14)
    at console.js:99:37
    at NativeModule.compile (node.js:395:5)
    at Function.NativeModule.require (node.js:340:18)
    at node.js:223:27
    at Object.<anonymous> (/usr/lib/node_modules/npm/node_modules/uid-number/get-uid-gid.js:16:1)
    at Module._compile (module.js:413:34)

    at /usr/lib/node_modules/npm/node_modules/uid-number/uid-number.js:37:16
    at ChildProcess.exithandler (child_process.js:209:5)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at maybeClose (internal/child_process.js:850:16)
    at Socket.<anonymous> (internal/child_process.js:323:11)
    at emitOne (events.js:90:13)
    at Socket.emit (events.js:182:7)
    at Pipe._onclose (net.js:475:12)

Sorry for all the error messages, just trying to post as much information for you guys as possible.

russalex · 2016-04-07T02:34:32Z

Actually, love the info. Thanks!

I'll take this up to the devs tomorrow. The fact that you're seeing the socket error makes me think that we have a bug someplace in our code. I'll make certain it gets to the right place.

jokeyrhyme · 2016-04-07T05:20:33Z

Related to #6 and/or #9 ?

mike-morr · 2016-04-07T06:39:51Z

@russalex This could be an issue with running the command as root. I was getting the same stack and the same "could not get uid/gid" running:

npm install npm -g

I found these switches --user and --unsafe-perm

unsafe-perm

Default: false if running as root, true otherwise

Type: Boolean

Set to true to suppress the UID/GID switching when running package
scripts. If set explicitly to false, then installing as a non-root user
will fail.

user

Default: "nobody"

Type: String or Number

The UID to set to when running package scripts as root.

When I executed:

npm --user root --unsafe-perm true install npm -g

It gets all the way to the end and fails.

I tried again with a few different accounts existing and non-existing. It always makes it to the end and fails with this:

root@localhost:~# npm --user sync --unsafe-perm true install npm -g
- [email protected] node_modules/npm/node_modules/async-some
npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "--user" "sync" "--unsafe-perm" "true" "install" "npm" "-g"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! path /usr/lib/node_modules/npm
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall rename

npm ERR! Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm.DELETE'
npm ERR!     at moveAway (/usr/lib/node_modules/npm/lib/install/action/finalize.js:38:5)
npm ERR!     at destStatted (/usr/lib/node_modules/npm/lib/install/action/finalize.js:27:7)
npm ERR!     at FSReqWrap.oncomplete (fs.js:82:15)
npm ERR!
npm ERR! Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm.DELETE'
npm ERR!     at Error (native)
npm ERR!  [Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm.DELETE']
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     /root/npm-debug.log

I've got to call it a night, but I will try to look into it more tomorrow. Hopefully someone will have a workaround by then.

russalex · 2016-04-07T17:19:53Z

Ok, good news and bad news.

First the good news. Running through the steps on /tmp on one of our dev branches. Looks like there's a fix inbound. This morning I was able to:

/tmp$ npm install acorn
/tmp
└── [email protected]

npm WARN enoent ENOENT: no such file or directory, open '/tmp/package.json'
npm WARN tmp No description
npm WARN tmp No repository field.
npm WARN tmp No README data
npm WARN tmp No license field.

Bad news is that this does not work through /mnt/c. I'll need to write a bug on that one.

The team is hard at work fixing bugs. Every build we put out should have visible improvements. Not certain when this one will hit the insider flight, but it is inbound.

EvHaus · 2016-04-07T20:50:57Z

@russalex Thanks for the update! When files are written to / where do they actually go? Somewhere on the C: partition? Will files written to / disappear if Bash on Windows is uninstalled?

jgchristopher · 2016-04-08T22:41:24Z

#14

I believe these are related.

mickeyinfoshan · 2016-04-11T05:07:36Z

@Buck-Rawgers I got the same issue even --user root is used and run my bash as Administrator. Any ideas?

npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "--user" "sync" "--unsafe-perm" "true" "install" "npm" "-g"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! path /usr/lib/node_modules/npm
npm ERR! code EACCES
npm ERR! errno -13
npm ERR! syscall rename

npm ERR! Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm.DELETE'
npm ERR!     at moveAway (/usr/lib/node_modules/npm/lib/install/action/finalize.js:38:5)
npm ERR!     at destStatted (/usr/lib/node_modules/npm/lib/install/action/finalize.js:27:7)
npm ERR!     at FSReqWrap.oncomplete (fs.js:82:15)
npm ERR!
npm ERR! Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm.DELETE'
npm ERR!     at Error (native)
npm ERR!  [Error: EACCES: permission denied, rename '/usr/lib/node_modules/npm' -> '/usr/lib/node_modules/.npm.DELETE']
npm ERR!
npm ERR! Please try running this command again as root/Administrator.

npm ERR! Please include the following file with any support request:
npm ERR!     /root/npm-debug.log

jgchristopher · 2016-04-11T15:04:19Z

@Buck-Rawgers until a update comes out fixing symlinks, there isn't much to do at this point.

trevren11 · 2016-04-11T16:47:12Z

@EvNaverniouk go to %LOCALAPPDATA%\lxss\root and you will find the files that you are looking for (if I understood the first part of your most recent question).

592da · 2016-04-17T10:00:00Z

any solution available ?

EvHaus · 2016-04-17T19:12:15Z

@592da Apparently the Microsoft team has been making some progress here. We're waiting for a new update to Bash on Windows to give it another try. But so far it sounds like if you want to use npm you will need to do it on files in / and NOT on your mounted /mnt/* drives. Which is a bit of a bummer but still better than nothing. We have to wait and see what the team can do.

russalex · 2016-04-22T20:38:58Z

New build is out :http://aka.ms/wip14328
Release notes for Bash on Ubuntu on Windows are here: https://msdn.microsoft.com/en-us/commandline/wsl/release_notes

I can confirm that npm working (without -g) on / is in the build. Getting these links on /mnt/ is working internally and will soon get onto the release pipeline. No ETA on when it will hit the public.

Keeping this one open until full solution hits the public.

EvHaus · 2016-04-23T04:18:14Z

@russalex Did some testing on Build 14328 and can confirm your notes

✅ npm install acorn (and many other packages I tried) works in /tmp
😢 npm install -g acorn still doesn't work (same uv_pipe_open error)
😢 npm install acorn still doesn't work in /mnt/* (same symlink operation not permitted error)

Amazing work so far! And incredible community outreach from the Microsoft team working on this project. Really excited to try out the next public release.

askbeka · 2016-04-23T14:23:38Z

Still having an symlink error on /mnt on build 14328

honwhy · 2016-04-23T15:00:27Z

does not work for

npm install -g tldr

pgrm · 2016-04-23T23:18:06Z

I've "fixed" npm to install global packages into the home directory via .npmrc

prefix=/home/peter/.npm-packages

Now I'm getting a new error when I try installing any package:

npm install -g yo

npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm
npm ERR! Linux 3.4.0+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "yo"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! code EIO

npm ERR! EIO: i/o error, read
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /home/peter/npm-debug.log

npm --version
3.8.3
node --version
v5.10.1

kleinesfilmroellchen · 2022-07-02T18:49:38Z

This is STILL an issue in 2022. Debian 12, 4.19.128-microsoft-standard #1 SMP Tue Jun 23 12:58:10 UTC 2020 x86_64 GNU/Linux, nodejs v16.15.1, npm 8.13.1.

EvHaus changed the title ~~Unable to install acorn npm package~~ Unable to install acorn npm package (inability to symlink on mounted drives) Apr 7, 2016

This was referenced Apr 7, 2016

tar with symbolic links #9

Closed

Symlink woes #6

Closed

filipeaguiar mentioned this issue Apr 10, 2016

Problem with Nodejs > npm install #96

Closed

russalex mentioned this issue Apr 12, 2016

npm package fails to install "npm ERR! Error: EACCES: permission denied" #14

Closed

Sparticuz mentioned this issue Apr 12, 2016

npm install failing. Symlink problems? MicrosoftDocs/WSL#26

Closed

karacaenes mentioned this issue Apr 13, 2016

Rename syscall broken for non-empty directories #163

Closed

ShakataGaNai mentioned this issue Apr 14, 2016

Can't install meteor or docker #180

Closed

benhillis mentioned this issue Apr 19, 2016

"bower install --allow-root" install fails with " EINVAL: invalid argument, rename" #152

Closed

luxzg mentioned this issue Jul 11, 2021

WSL IP address & Subnet is never deterministic (Constantly changing) #4467

Open

BurnutsGaming mentioned this issue Aug 8, 2021

WSL Fails to mount file system after first setting up Ubuntu for WSL. #7284

Closed

2 tasks

gmqiyue mentioned this issue Aug 26, 2021

WSL2 failed to run, no channels available for device drvfs #7352

Closed

2 tasks

alexandretrentesaux mentioned this issue Sep 16, 2021

WSL2 failed to mount /mnt/c after update to Windows11 #7431

Closed

akash07k mentioned this issue Sep 18, 2021

An error occurred mounting one of your file systems. Please run 'dmesg' for more details. #7435

Closed

2 tasks

reyesvicente mentioned this issue Jan 23, 2022

An error occurred mounting one of your file systems. Please run 'dmesg' for more details. #7960

Closed

2 tasks

This was referenced Feb 8, 2022

Offline install Ubuntu failing #7489

Closed

Offline distribution #8031

Open

thep0y mentioned this issue Feb 24, 2022

An error occurred mounting one of your file systems. Please run 'dmesg' for more details. After importing Ubuntu Distro #8077

Closed

2 tasks

sameerkattel mentioned this issue Mar 10, 2022

WSL stopped working after latest windows update #8133

Closed

2 tasks

MilesTFox mentioned this issue Mar 28, 2022

No Internet with WSL on system with multiple LAN addresses #8202

Closed

2 tasks

penguinpages mentioned this issue Mar 30, 2022

WSL Bridge - Packet Diagram #8208

Closed

2 tasks

zouherenjie mentioned this issue Mar 31, 2022

Can't mount a disk that doesn't have any partitions. Fails to mount with error code: 22 #8215

Closed

2 tasks

huiyeruzhou mentioned this issue Apr 7, 2022

Cannot mount disk to wsl #8246

Closed

2 tasks

mastercoms mentioned this issue Apr 11, 2022

Cannot visit localhost port #8270

Closed

daveblake mentioned this issue Jun 14, 2022

Cannot access filesystem through explorer - \\wsl.localhost\Ubuntu\mnt #8512

Closed

2 tasks

mprevot mentioned this issue Jun 30, 2022

Very slow startup (40 seconds) #8569

Open

2 tasks

dragonkali mentioned this issue Jul 3, 2022

WSL 2 unable to mount windows partition after they were moved. #5715

Closed

Frederik-Edel mentioned this issue Jul 31, 2022

nl80211 isnt part of Kernel #8671

Closed

2 tasks

Macmee mentioned this issue Aug 22, 2022

Slow startup #8751

Closed

2 tasks

imia-dbitsch mentioned this issue Aug 30, 2022

WSL not starting after upgrading to latest Insider Build #8781

Closed

2 tasks

exitdown mentioned this issue Nov 23, 2022

enabling systemd on wsl2 under 22h2 results in extreemly bad performance (suspect some kind of io issue) #9029

Closed

ghost mentioned this issue Dec 12, 2022

Can't install WSL from the command prompt #9314

Closed

2 tasks

3axap4eHko mentioned this issue Dec 14, 2022

Processing fstab with mount -a failed for bound directories #9321

Closed

2 tasks

csy2002 mentioned this issue Jun 18, 2023

upgrade WSL2 to a custom kernel，I encountered the error 'Error code: Wsl/Service/CreateInstance/CreateVm/HCS_E_CONNECTION_TIMEOUT' #10212

Closed

2 tasks

imag0r mentioned this issue Dec 31, 2023

WSL2 cold start super slow (almost 1 minute) #10966

Closed

2 tasks

kaiwi mentioned this issue Feb 18, 2024

segfault - Unable to launch WSL2 Distro #11174

Closed

2 tasks

JustLookAtNow mentioned this issue Jul 22, 2024

Error code: Wsl/Service/CreateInstance/CreateVm/WSAENOTCONN Press any key to continue... #11791

Open

2 tasks

HamzaHajeir mentioned this issue Sep 18, 2024

Built WSL do not include bluetooth controller of Mediatek #12048

Closed

2 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Unable to install `acorn` npm package (inability to symlink on mounted drives) #3

Unable to install `acorn` npm package (inability to symlink on mounted drives) #3

EvHaus commented Apr 7, 2016

mike-morr commented Apr 7, 2016

EvHaus commented Apr 7, 2016

EvHaus commented Apr 7, 2016

russalex commented Apr 7, 2016

EvHaus commented Apr 7, 2016

russalex commented Apr 7, 2016

jokeyrhyme commented Apr 7, 2016

mike-morr commented Apr 7, 2016

unsafe-perm

user

russalex commented Apr 7, 2016

EvHaus commented Apr 7, 2016

jgchristopher commented Apr 8, 2016

mickeyinfoshan commented Apr 11, 2016

jgchristopher commented Apr 11, 2016

trevren11 commented Apr 11, 2016

592da commented Apr 17, 2016

EvHaus commented Apr 17, 2016

russalex commented Apr 22, 2016

EvHaus commented Apr 23, 2016 •

edited

Loading

askbeka commented Apr 23, 2016

honwhy commented Apr 23, 2016

pgrm commented Apr 23, 2016

kleinesfilmroellchen commented Jul 2, 2022

Unable to install acorn npm package (inability to symlink on mounted drives) #3

Unable to install acorn npm package (inability to symlink on mounted drives) #3

Comments

EvHaus commented Apr 7, 2016

mike-morr commented Apr 7, 2016

EvHaus commented Apr 7, 2016

EvHaus commented Apr 7, 2016

russalex commented Apr 7, 2016

EvHaus commented Apr 7, 2016

russalex commented Apr 7, 2016

jokeyrhyme commented Apr 7, 2016

mike-morr commented Apr 7, 2016

unsafe-perm

user

russalex commented Apr 7, 2016

EvHaus commented Apr 7, 2016

jgchristopher commented Apr 8, 2016

mickeyinfoshan commented Apr 11, 2016

jgchristopher commented Apr 11, 2016

trevren11 commented Apr 11, 2016

592da commented Apr 17, 2016

EvHaus commented Apr 17, 2016

russalex commented Apr 22, 2016

EvHaus commented Apr 23, 2016 • edited Loading

askbeka commented Apr 23, 2016

honwhy commented Apr 23, 2016

pgrm commented Apr 23, 2016

kleinesfilmroellchen commented Jul 2, 2022

Unable to install `acorn` npm package (inability to symlink on mounted drives) #3

Unable to install `acorn` npm package (inability to symlink on mounted drives) #3

EvHaus commented Apr 23, 2016 •

edited

Loading