Yarn: Error: EROFS: read-only file system, symlink

[himanshuphirke]

I don't understand why yarn is trying to setup and sym link !!

The code actually resides in location:
~/host/dev/mongo/hw1-3
Contents of yarn-error.log file:

Arguments:
/home/ubuntu/.nvm/versions/node/v6.10.1/bin/node /usr/share/yarn/bin/yarn.js install

PATH:
/home/ubuntu/.nvm/versions/node/v6.10.1/bin:/home/ubuntu/bin:/home/ubuntu/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin

Yarn version:
0.21.3

Node version:
6.10.1

Platform:
linux x64

npm manifest:
{
"name": "hw1-3",
"version": "0.0.0",
"description": "Homework 1.3",
"main": "app.js",
"dependencies": {
"consolidate": "~0.13.1",
"crypto": "0.0.3",
"express": "~4.13.3",
"mongodb": "~2.1.3",
"nunjucks": "~2.2.0"
},
"author": "You",
"license": "0BSD",
"private": true
}

yarn manifest:
No manifest

Lockfile:
No lockfile

Trace:
Error: EROFS: read-only file system, symlink '../../../mime/cli.js' -> '/home/ubuntu/host/dev/mongo/hw1-3/node_modules/send/node_modules/.bin/mime'
at Error (native)

[dalsh]

Are you inside a VM ? May be related to this issue (929)

[himanshuphirke]

Yes
Its VM and not working on mounted partition

[dalsh]

Then I guess you should try adding --no-bin-links to your call

[bestander]

Is the workaround working?
If so I'll close the issue

[himanshuphirke]

Sorry about my typo in comment. But it's not working on mounted partition in a Virtual box VM

[bestander]

@himanshuphirke, does it work with --no-bin-links flag?
Could you explain the situation with the read-only FS? Why does it install node_modules fine but not the symlink?

[himanshuphirke]

The project folder is on a mounted partition. The OS on which this is worked is a Ubuntu VM (VirtualBox). The mounted partition works for installing only sym links are errored.

So in my first comment:
~/host

is a mounted partition

[bestander]

Thanks for clarification, @himanshuphirke, so the solution would be to disable symlinks inside node_modules completely?
I guess --no-bin-links flag should be the only solution

[himanshuphirke]

Isn't it a problem while installing over a VM partition? I mean there is a workaround but the original problem still exists

[queicherius]

For people coming here in search of an answer, you can also choose to allow symlinks for VirtualBox guests and yarn will work natively.