You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.
I got a problem with my npm install command where I'm getting issue described here.
I'm looking for a correct direction to solve this problem, but not sure what forum to select to report it, therefore I'm here with my next question.
npm install is working in the docker container (ubuntu:focal) and in the VirtualBox (Windows 10). But not in the shared nor mapped folders. The project must be placed in the inner virtual folder.
I don't think that it is the permissions issue as I set the project to 777 for all chmod -R 777 project.
npm v7 is working, but I've to use v6.
What can cause that the npm failing if running upon shared/mapped folder?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I got a problem with my
npm install
command where I'm getting issue described here.I'm looking for a correct direction to solve this problem, but not sure what forum to select to report it, therefore I'm here with my next question.
npm install
is working in the docker container (ubuntu:focal) and in the VirtualBox (Windows 10). But not in the shared nor mapped folders. The project must be placed in the inner virtual folder.I don't think that it is the permissions issue as I set the project to 777 for all
chmod -R 777 project
.npm v7 is working, but I've to use v6.
What can cause that the npm failing if running upon shared/mapped folder?
The text was updated successfully, but these errors were encountered: