No python virtualenv is available

usegalaxy.org support
1

While trying to issue the following command inside the forked galaxy repository,

$ sh run.sh

I get the following error

[admin@localhost galaxy]$ sh run.sh
Unsetting $PYTHONPATH
Activating virtualenv at .venv
Requirement already satisfied: pip>=8.1 in ./.venv/lib/python3.6/site-packages (20.1.1)
Looking in indexes: Package Index, Simple index
galaxy.dependencies.optional: no config file found
The Galaxy client has not yet been built and will be built now.
Installing node into /home/admin/Desktop/galaxy/.venv with nodeenv.
No python virtualenv is available

I have a pyenv environment using python 3.6.0 (local version for this directory: galaxy). The galaxy also sets up it’s own virtual environment inside ./.venv. I am not sure if the conflicting virtual environments are causing a roadblock here.

[admin@localhost galaxy]$ nodeenv .venv/
*Environment already exists: .venv/
[admin@localhost galaxy]$ source .venv/bin/activate
(.venv) [admin@localhost galaxy]$ sh run.sh
Unsetting $PYTHONPATH
Activating virtualenv at .venv
Requirement already satisfied: pip>=8.1 in ./.venv/lib/python3.6/site-packages (20.1.1)
Looking in indexes: Package Index, Simple index
galaxy.dependencies.optional: no config file found
The Galaxy client has not yet been built and will be built now.
Installing node into /home/admin/Desktop/galaxy/.venv with nodeenv.
No python virtualenv is available

Any comments?
Thanks in advance.

1 Like
2

Hi @shauryajauhari

This is probably the issue. Galaxy works best under Python 3.5 – and there were some prior issues with 3.6.

Could you try 1) removing both environments, 2) creating a new virtualenv .venv under /galaxy, then 3) executing sh run.sh.

You may be able to – or need to – skip step 2.

Related Q&A that still applies. It is the most basic way to start up that tends to work for most. The most current Galaxy release is 20.05, so swap that in. The rest is the same.

Thanks!