-
Notifications
You must be signed in to change notification settings - Fork 171
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
virtualenv venv OSError: [Errno 95] Operation not supported #173
Comments
Here is my guess: your Ubuntu 16.04.4 is running in a VM. You are trying to set up the virtualenv into a shared folder. That shared folder is shared with a Windows VM, and the filesystem of that share does not support symlinks. The fix would be: create your virtualenv within Ubuntu 16.04.4 not in |
@decidedlygray Oddly I have a very similar issue. I have mounted a myCloud drive to an Ubuntu 16.04 vm. This VM is actually sitting on top of a macOS (ie..host machine). The macOS is not sharing or accessing this mount point. I get the same error when I try to repo init on this mount. This is a 4TB cloud drive that I'd love to develop on. Thoughts? |
@johnsodd If it is that exact same error message, my first thought would be - the myCloud, for compatibility, probably came formatted as FAT or NTFS, neither of which support symlinks. Disk Utility on your mac, or the I would suggest taking everything you want to keep off of the myCloud drive, and reformatting it as
Dealer's choice on which way you want to go. Personally, I'd probably opt for option 1 personally because it's less complicated to set up, assuming symlinks work as expected. |
To use pipenv to manage Python virtual environments, which is also recommended by Python officially. Pipenv stores environmental files in user's home folder. This avoids the file system problems with shared folders. |
I created myproject folder manually in my HOME then ran sudo python3 -m venv myproject to create virtual env successfully |
After following the install instructions virtualenv venv on Ubuntu 16.04.4 leading to this issue:
Problems of Python 2 and 3? Any help is greatly appreciated.
The text was updated successfully, but these errors were encountered: