Upgrading 21.10.6 to 23.10.1 resulting in command not found #4783
Unanswered
Subject-13
asked this question in
Q&A
Replies: 1 comment
-
Digging through the Conda environments doc solved the problem. Since nextflow=22.08.0-edge it requires to set |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I recently tried out a new anaconda environment with nextflow=23.10.1. Also, I installed the same packages (also the same version) within the new environment. My nextflow call implies a variable
--env env.yaml
with all the required packages for mymain.nf
. When I run themain.nf
script, nextflow finds all selfmade scripts underbin/
, but can't find an installed tool (command not found). Nextflow creates the environment of myenv.yaml
, also installs the command-line tool it can't find. But it fails at this process. The process looks like:The error says:
BUT. When I run the same nextflow call with
NXF_VER=21.10.6
in front, within the same anaconda environment where I installed nextflow=23.10.1, the script runs without an error. That's why I'm wondering if it has something to do with the version. Do I oversee something or are there any big changes between those two used versions of nextflow?Thanks a lot in advance!
EDIT: In
nextflow.config
I define a profile withprocess.conda = "${params.env}"
for theenv.yaml
I pass through.Beta Was this translation helpful? Give feedback.
All reactions