/usr/bin/env: node: Permission denied

Question

As the title suggests I am receiving the error

/usr/bin/env: node: Permission denied

when trying to run

npm run build

for my react app. The following link is the leadup to this point with all that I've done and tried, not to be included here for the sake of not duplicating questions Error with react-scripts in npm run build.

Additionally, I have viewed this posting, Getting Error /usr/bin/env: node : Permission Denied, and it was unhelpful to me.

Any help is much appreciated.

This sounds like your `node` executable isn't, well, executable. Try `which node` to see which `node` your computer is trying to run; chances are it's not something in e.g. `/usr/bin` or `/usr/local/bin` if this is the symptom. — AKX, Jan 31 '22 at 20:18
-rwxr-xr-x 1 mod mod 81232432 Jan 18 13:48 /root/.nvm/versions/node/v17.4.0/bin/node @md2perpe — ABadOmelette, Jan 31 '22 at 20:24
/root/.nvm/versions/node/v17.4.0/bin/node is what pops up. Should I look up how to make it a an executable file then? @AKX — ABadOmelette, Jan 31 '22 at 20:25
The rights `-rwxr-xr-x` tell us that `node` is executable. What happens if you run `node` or `/root/.nvm/versions/node/v17.4.0/bin/node` (try both)? — md2perpe, Jan 31 '22 at 20:27
Sorry if this sounds dumb but what do you mean by run node? @md2perpe — ABadOmelette, Jan 31 '22 at 20:30
Type those as commands in the console, just as you did with `ls -l "$(which node)"`. — md2perpe, Jan 31 '22 at 20:32
@md2perpe I had no idea node had its own prompt window, learn something new every day. This is what pops up for just node, same for folder Welcome to Node.js v17.4.0. Type ".help" for more information. > — ABadOmelette, Jan 31 '22 at 20:35
@md2perpe so if thats the case what could be the other possibilities for the problem? — ABadOmelette, Jan 31 '22 at 20:42
Alright, I appreciate the effort, I'll give it a day or 2 to see if anyone else chimes in @md2perpe — ABadOmelette, Jan 31 '22 at 20:49
@md2perpe It does the same thing as just executing node normally — ABadOmelette, Feb 01 '22 at 15:23
Run `hash -r` (assuming you're using bash as shell) and see if `/usr/bin/env node` still works after that. — md2perpe, Feb 01 '22 at 19:02
https://stackoverflow.com/questions/51811564/sh-1-node-permission-denied — Raman Joshi, Jan 20 '23 at 14:41

score 12 · Answer 1 · answered May 20 '22 at 19:06

12

I was working in a dockerized node environment and noticed that the mounted source code directory had different ownership (running the container as root) from host environment. Changing the ownership using:

chown -R root:root .

made the error go away for me!

answered May 20 '22 at 19:06

Raaka

304
1
3
15

1

solved it for me – blockhead Jun 23 '22 at 17:58
How do make this permanent? it seems i have to run that every time i ssh into the server. I am not even working a dockerized environment. – blockhead Jun 26 '22 at 13:29
Once you run the command, it should be permanent. Unless, some other process is changing the permissions again? – Raaka Sep 30 '22 at 12:51
https://stackoverflow.com/questions/51811564/sh-1-node-permission-denied – Raman Joshi Jan 20 '23 at 14:41
After the chown, I needed to add `--unsafe-perm` to my npm command to make it work eg `npm run prod --unsafe-perm` – Mtxz Mar 21 '23 at 02:22

score 3 · Accepted Answer · answered Apr 06 '22 at 13:13

3

The issue ended up being a matter of file ownership. Root was the owner of many things for the project rather than my profile. Simply changed the ownership from root to me.

answered Apr 06 '22 at 13:13

ABadOmelette

151
1
1
10

https://stackoverflow.com/questions/51811564/sh-1-node-permission-denied – Raman Joshi Jan 20 '23 at 14:41

score 1 · Answer 3 · answered Mar 22 '22 at 22:08

1

For me, re-installing node with NVM solved the issue:

Install nvm
nvm install 14
nvm use 14

answered Mar 22 '22 at 22:08

DaWe

1,422
16
26

score 0 · Answer 4 · answered Oct 09 '22 at 15:14

For anyone else hitting this, there is another avenue of investigation. There might be another factor affecting execute permissions. There's an exec flag on drive mounts to enable script execution (neat safety feature for automounted usb sticks!). So if your code is on a drive that you've mounted, you need that option set to run scripts on it. Tell-tale signs are the permissions on the script being correct (appropriate user, group and execute bits set), but it still complaining about the shebang line (1st line) being the permission denied. Also, if you type mount, you might see noexec set on the mount point where your source code is (it may not show here if exec is set). How your mount is set up varies greatly, but a place to start is your /etc/fstab.

score -2 · Answer 5 · answered Jul 18 '22 at 15:04

-2

you should running command as super user sudo npm run build

answered Jul 18 '22 at 15:04

Yogi Pristiawan

13
1
7

/usr/bin/env: node: Permission denied

5 Answers5