Npm install issue on Virtualbox with Ubuntu installed

Question

Just wonder if anyone could shed some light on npm install running on Virtualbox machine (with Ubuntu v16.4 installed).. I'm getting this sorry of error

osboxes@osboxes:/media/sf_ubuntu/angular$ npm install
[email protected] /media/sf_ubuntu/angular
├── UNMET PEER DEPENDENCY @angular/[email protected]
└── UNMET PEER DEPENDENCY @angular/[email protected]

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN [email protected] requires a peer of @angular/compiler@~2.1.1 but none was installed.
npm WARN [email protected] requires a peer of @angular/core@~2.1.1 but none was installed.
npm WARN [email protected] No repository field.
npm ERR! Linux 4.8.0-22-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install"
npm ERR! node v6.9.1
npm ERR! npm  v3.10.8
npm ERR! path ../acorn/bin/acorn
npm ERR! code EROFS
npm ERR! errno -30
npm ERR! syscall symlink

npm ERR! rofs EROFS: read-only file system, symlink '../acorn/bin/acorn' -> '/media/sf_ubuntu/angular/node_modules/.bin/acorn'
npm ERR! rofs This is most likely not a problem with npm itself
npm ERR! rofs and is related to the file system being read-only.
npm ERR! rofs 
npm ERR! rofs Often virtualized file systems, or other file systems
npm ERR! rofs that don't support symlinks, give this error.

npm ERR! Please include the following file with any support request:
npm ERR!     /media/sf_ubuntu/angular/npm-debug.log
npm ERR! code 1

what is /media/sf_ubuntu/angular ? Is it a network path or a removable drive? If so you need to check its permissions. — jsalatas
– jsalatas, Commented Dec 6, 2016 at 0:53
It appears to be a permission issue. I had to move the package.json to a folder inside ubuntu HDD. It run okay now. Thanks — Hung Bui
– Hung Bui, Commented Mar 7, 2018 at 13:11

pirs · Accepted Answer · 2017-11-13 03:59:29Z

3

Virtualbox limits the creating of symlink in shared directory in terms of safety. So you should open relevant feature:

Close Virtualbox
Add the installation path of Virtualbox to environment variable PATH
Execute the command below in cmd

VBoxManage setextradata <VM_NAME> VBoxInternal2/SharedFoldersEnableSymlinksCreate/<SHARE_NAME(without the sf_ prefix)> 1
Run Virtualbox with admin

edited Nov 13, 2017 at 3:59

pirs

2,4612 gold badges20 silver badges25 bronze badges

answered Nov 13, 2017 at 2:55

Sevenskey

463 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Sevenskey Over a year ago

Somehow the code showing above is incomplete. Complete code here. VBoxManage setextradata <VM_NAME> VBoxInternal2/SharedFoldersEnableSymlinksCreate/<SHARE_NAME(without the 'sf_' prefix)> 1

Collectives™ on Stack Overflow

Npm install issue on Virtualbox with Ubuntu installed

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related