-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error: EACCES: permission denied, mkdir '/network/workspace/.config' #9
Comments
Hey @uaktags, |
machine is a VM /home/tim is the current user's (myself) home directory and gala is correctly permissioned Steps to reproduce:
|
It may be this issue, from a yeoman dependency somewhere in fablo. |
Hmm, so just to clarify, this is a normal VM, not WSL or a container. Permissions definitely seems to be a concern here, if I cd into the test-network directory, and sudo call ./fablo up, it'll get through the process further but will still fail on With this in mind, i'm wondering if the sdk was tested by a root user with a global install of node rather than nvm? However, the weird part is that the original, non-sudo, permission is denied error is on /network/workspace, which according to fablo is a virtual directory that is actually from in the docker
|
I missed the part about it being installed globally in the yeoman bug; it was a similar call stack, and I got excited. I run nvm (installed via homebrew), though I am on macOS and do not have this issue. |
When attempting to start the network, it fails with the permissions issue above. This is after following the current "Getting Started" guide: https://github.com/GalaChain/sdk/blob/main/docs/getting-started.md
The text was updated successfully, but these errors were encountered: