[conda] Can I change (or enforce) the conda version in an env?

[Carter Sanders]

Hello-

Does anybody know if setting the conda version in an env yml file has any
effect? E.g. conda=4.4.11=<python qualifier>
I've confirmed I can run with it, but it doesn't seem to indicate the conda
version has been change if the conda version in the yml

Thanks in advance for any help.

-Carter

[Chris Withers]

Post by Carter Sanders
Hello-
Does anybody know if setting the conda version in an env yml file has
any effect? E.g. conda=4.4.11=<python qualifier>
I've confirmed I can run with it, but it doesn't seem to indicate the
conda version has been change if the conda version in the yml

I'm pretty sure that conda itself can only installed in the root
environment. I find that a little annoying myself, but I do understand
the choice.

cheers,

Chris

[Carter Sanders]

Thanks, for the advice, Kale.

OK. So given that, if I have a jenkins build slave with three executors,
should I create one conda installation per build executor, so that any
running process doesn't share a conda installation with another process?
There doesn't seem to be a way to create a read-only miniconda
installation. When I chmod it or have it owned by root, any attempt to
create or update an environment fails when it tries to write metadata. One
of my issues is that I can't seem to block a running process from doing a
"conda install conda=<conda_version>"

Also, one thing I'm trying to do inside of the yml is something like the maven
enforcer plugin <https://maven.apache.org/enforcer/maven-enforcer-plugin/>
does - enforce the tools version. Conda can do that with the python version
(and also install the needed version), but it's not clear how to enforce
the conda version. I don't necessarily want to change the conda version
from inside the yml (and I appreciate your warning that this is a bad idea)
, but I would like to be able to exit and report a failure if the conda
version is discovered to be wrong.

Post by Carter Sanders
Does anybody know if setting the conda version in an env yml file has any
effect?
Mixing management of conda itself with conda-env and environment.yml files
is asking for trouble. I know of at least one issue off the top of my head,
and there are probably several more.
I’m pretty sure that conda itself can only installed in the root
environment.
As of conda 4.4 that’s not longer true. But if you’re going to install
conda in multiple environments, you’ve got to be particularly careful with
*which* conda you’re hitting at any particular time, and where the
pkgs_dirs and envs_dirs are pointing. Make liberal use of type -a, which
-a, and where.
​

Post by Chris Withers

Post by Carter Sanders
Hello-
Does anybody know if setting the conda version in an env yml file has
any effect? E.g. conda=4.4.11=<python qualifier>
I've confirmed I can run with it, but it doesn't seem to indicate the
conda version has been change if the conda version in the yml

I'm pretty sure that conda itself can only installed in the root
environment. I find that a little annoying myself, but I do understand the
choice.
cheers,
Chris
--
You received this message because you are subscribed to the Google Groups
"conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an
Visit this group at https://groups.google.com/a/continuum.io/group/conda/
.
To view this discussion on the web visit
https://groups.google.com/a/continuum.io/d/msgid/conda/cb55001c-1d00-f925-dda4-2253f33cbbd4%40withers.org
.
For more options, visit https://groups.google.com/a/continuum.io/d/optout
.