protocol error setting up virtualenvironment through vagrant on ubuntu

Question

I'm trying to set up a virtualenv on Ubuntu 12.04 with Python 2.7 using vagrant but having same issues. it seems like this issues is seen only when "vagrant up" is issued from windows. what is the solution? any pointers?

New python executable in .vagrant-env/bin/python
  Traceback (most recent call last):
  File "/usr/local/bin/virtualenv", line 9, in <module>
    load_entry_point('virtualenv==1.11.6', 'console_scripts', 'virtualenv')()
  File "/usr/local/lib/python2.7/dist-packages/virtualenv.py", line 824, in main
    symlink=options.symlink)
  File "/usr/local/lib/python2.7/dist-packages/virtualenv.py", line 984, in   create_environment
    site_packages=site_packages, clear=clear, symlink=symlink))
  File "/usr/local/lib/python2.7/dist-packages/virtualenv.py", line 1404, in install_python
    os.symlink(py_executable_base, full_pth)
   OSError: [Errno 71] Protocol error

Cure

seems like its related to this .. but i can't find the answer to solve this issue #5907859 – Cure

Has anybody tried solving it with pythonbrew? if so how ? – Cure

Did you get this fixed? – Marcel

Answer 1

The solution is to use --always-copy. See here for the gory details.

Bosh

Answer 2

This error can be fixed if you create the virtual env outside the /vagrant/ shared folder...

If go to the home folder of your vagrant user, you can create the virtualenv in there without this problem!

Just the venv must be out of this /vagrant/ directory... after that you can go work as usually activating this venv and working with your sorce code in the usual /vagrat/ shared dir...

Tent

Answer 3

I found the issue and fixed it. Just start your git bash/cmd prompt console as an administrator. Then, vagrant up > setup your virtual env. It should be a cake walk.

Thanks Venkat

Zomba

This is the root of the problem. – Inerney

(sorry for the bumping of a 6-year-old post) I believe this is also the solution for other ways to setup a venv (notably python3 -m venv venv) – Underdeveloped

Answer 4

Use this

virtualenv --python= <#Python path for specific version#> <#Folder name#> --always-copy

Example:

virtualenv --python=/usr/local/bin/python3.7 venv --always-copy

Fouquiertinville

Answer 5

I have had a similar problem. Just restarting the vagrant box was enough to solve it.

Eclat

Answer 6

virtualenv venv --python=python3

Morceau

While this code may answer the question, providing additional context regarding how and/or why it solves the problem would improve the answer's long-term value. – Crackle

Answer 7

This worked for me:

sudo virtualenv venv

Tussle