-
Notifications
You must be signed in to change notification settings - Fork 683
Conda Unable to Create Environment #5947
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
Comments
Installing Conda 25.1.1 resulted in successful creation of the environment and a successful run of the code, further supporting the likelihood of an incompatibility with Conda 25.3.0. |
Thanks for this troubleshooting. If I'm understanding correctly they have restored it in 4.6 stating this conda/conda#7211. In this case the better thing to do it so add a warning in the docs. /cc @christopher-hakkaart |
According to: https://github.com/conda/conda/blob/3259a9c914446a44b12e7c4fa191972892b8e394/CHANGELOG.md#2530-2025-03-17 |
Thanks @danpal96 , I'll double check this and update the docs accordingly. |
I was working on a pipeline of my own, and I discovered that this issue also appears to be present for Mamba (2.1.0), where it also throws the error:
I have not yet tried older versions of Mamba, but unlike Conda I am not able to find a specific changelog note of Mamba removing --mkdir, but it could just be that I haven't dug far enough. |
I've been testing this today and agree with @danpal96 that It looks like it was a warning that it would be depreciated from 25.3.0 onwards. I can't see anything suggesting it would be added back. |
Bug report
As some backing information, I encountered this bug during the Nextflow Training 2.1.3 Part 6 (https://training.nextflow.io/2.1.3/hello_nextflow/06_hello_config/). I am intending on using either Singularity/Apptainer containers or defined Conda environments, and this bug poses a problem for the Conda possibility and for the training.
Expected behavior and actual behavior
Expected behavior: Running
nextflow run hello-config.nf
in "Part 6 Section 1.3. Run the workflow to verify that it can use Conda" should result in successful execution of the workflow.Actual behavior: Running
nextflow run hello-config.nf
in "Part 6 Section 1.3. Run the workflow to verify that it can use Conda" results in an error, failing to create a Conda environment.Steps to reproduce the problem
All steps as-written in Nextflow Training 2.1.3.
Program output
.nextflow.log
Environment
Additional context
After doing some digging, this may be related to the version of Conda I am running (Conda 25.3.0). According to the Release Notes (https://docs.conda.io/projects/conda/en/stable/release-notes.html#deprecations),
I believe this error is related to Nextflow attempting to still use the "--mkdir" argument. Would there be any way to create a workaround, or should I attempt to install a version of Conda prior to 25.3.0?
The text was updated successfully, but these errors were encountered: