Conda environment not named
1
0
Entering edit mode
12 months ago

I have installed snakemake with conda as following:

conda create --yes -c conda-forge -c bioconda -n snakemake snakemake   

But the environment has not the name "snakemake" I have put in the above command. There is only the full path indicated.

 conda info --envs                                     
# conda environments:                                                         
# base                  *  /mnt/shared/home/usr/mambaforge     
    mamba                  /mnt/shared/home/usr/mambaforge/envs/mamba                    
                           /mnt/shared/scratch/usr/apps/conda                            
                           /mnt/shared/scratch/usr/apps/conda/envs/snakemake

And I have to call it using the full path to call the snakemake environment.

Would anyone know why the environment is not named?

snakemake conda • 836 views
ADD COMMENT
3
Entering edit mode
12 months ago
Nitin Narwade ★ 1.6k

There are two different conda installations on your system. When you are activating an environment from one conda (/shared/home/usr/mambaforge) the other (/mnt/shared/scratch/usr/apps/conda) is not loading properly, as it may have misconfigured with the same configuration file in /home/user/.conda. This could be one of the possible explanations.

I think you can still activate these environments using a complete path.

Regards,
Nitin N.

ADD COMMENT
0
Entering edit mode

Thank you Nitin. I though that /mnt/shared/home/usr/mambaforge was just in my base environment, and /mnt/shared/scratch/usr/apps/conda just accessible in the mamba environment.

In this case, do you think the best fix would be to erase the /mnt/shared/scratch/usr/apps/conda file?

ADD REPLY
2
Entering edit mode

Yes, I would prefer keeping only one conda installation on a system.

Regards,

Nitin N.

ADD REPLY

Login before adding your answer.

Traffic: 2434 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6