-
Notifications
You must be signed in to change notification settings - Fork 642
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
useMicromamba
option doesn't work - generates Conda instructions instead.
#4161
Comments
Fair enough, should be a simple fix. Fwiw, I've been using Mambaforge which provides mamba as a drop-in replacement for |
Do you mean miniforge? Not sure it's the same it says
In any case the the support for micromamba should be honoured as described in the docs |
Mambaforge is miniforge with mamba as the default |
Unable to replicate. Nextflow uses
|
I think there is still a bug here though: nextflow/modules/nextflow/src/main/groovy/nextflow/executor/BashWrapperBuilder.groovy Lines 430 to 437 in 7d6ad62
The problem was never that the conda builder doesn't use micromamba, but that the bash wrapper uses |
I can reproduce the two bugs discussed above:
Would be great to get a nextflow release that fixes these! |
Thanks @shenker . Regarding the nextflow/modules/nextflow/src/main/groovy/nextflow/conda/CondaCache.groovy Lines 284 to 296 in 89ede15
I think it is not added for |
Yes, |
Should be solved in #4302 and released in
Full output
|
You may be able to use the workaround described here: #4161 (comment) - set |
Bug report
Expected behavior and actual behavior
According to the docs, the useMicromamba directive should cause Nextflow to use Micromamba instead of Conda.
When using this option, the nextflow process fails to run, because the generated
.command.run
file still usesconda
.Steps to reproduce the problem
On a machine with micromamba installed, but not conda:
Program output
The .nextflow.log file, as well as the generated .command.* files are in the gist referenced above. (e.g: https://gist.github.com/jemma-nelson/921e3a8aa32efe22bd73fbe1cbdfd09b#file-nextflow-log)
Program output:
Environment
Additional context
I mentioned this in slack last week, but did not get any attention. https://nextflow.slack.com/archives/C02T98A23U7/p1690325743801519
As near as I can tell from examining the source code, this configuration option cannot work, nor can the
useMamba
option, as nextflow always emitsconda info --json
for conda activation.You may also want to add
--yes
to themicromamba create
command, because ifexport MAMBA_ALWAYS_YES=true
is not set, environment creation will hang indefinitely.The text was updated successfully, but these errors were encountered: