EACCESS on "rename" unique to ARM64 (Surface Pro X machine)

[pr3johns]

• Your Windows build number: 10.0.19041.207

• What you're doing and what's happening: I am attempting an npm install for a React project. Part of the install involves a rename system call which always fails (full screen shot here):

I am also attaching the npm log.

2020-04-26T21_37_47_987Z-debug.log

I have also successfully ran the same npm install on the EXACT same project on an Intel machine inside WSL without ANY permission issue. Is there something particular to ARM64 WSL?

Thanks.

[sirredbeard]

Could you please attach an strace?

$ strace -o strace.log yourfailingcommand

[pr3johns]

Here you go....
strace.zip

[pr3johns]

Also I'd be happy to post this project on github if someone wants to repro.

[sirredbeard]

A repro would be very useful.

[pr3johns]

OK I was able to distill this to the simplest possible repro. Perform these steps:

npm init
npm install grpc

(just accept all defaults to the npm init). Running these commands in WSL on an ARM64 machine FAILS with the same EACCESS screenshot shown in my original post. Running this command on an Intel device in WSL works. Both machines running npm 6.14.4.

[sirredbeard]

Duplicate of #14.

[pr3johns]

I read all the comments in issue #14 (there are a lot!). None of the suggestions worked for me EXCEPT someone suggested that the issue is not prevalent on WSL2. I upgraded to WSL2 and the issue went away. Thanks.

[therealkenc]

Yeah that's #14 aka #1529 aka others. I should have looked at the screencap closer and was thrown by unique to Arm.