[conda] Is it safe to do a "conda install conda=<version>" while another process uses the conda installation?

[Carter Sanders]

The title pretty much says it all. I'm running a ci machine with multiple
executors running a single conda installation. If one changes the conda
version using the "conda install conda=<version>" command, will it
interrupt or affect another processes running in a different conda env
which uses the same conda installation.

Thanks in advance -
Carter

[Chris Withers]

Post by Carter Sanders
The title pretty much says it all. I'm running a ci machine with
multiple executors running a single conda installation. If one changes
the conda version using the "conda install conda=<version>" command,
will it interrupt or affect another processes running in a different
conda env which uses the same conda installation.

If I were building a CI system around conda in the way it sounds like
you are, I'd have a single job that kept conda up to date, and run it,
say, once a day.

Unlikely virtualenv and pip, the conda command line utility doesn't form
part of any of the individual environments.

I'd say that, provided your jobs testing packages or projects are each
using their own environment, updating conda in the root environment
should be fine, even if the conda-update job runs at the same time as
one of them.

cheers,

Chris

[Chris Withers]

You might want to consider locking down the root environment as
read-only.

What's the recommended way of doing that? I've accidentally installed
crap into my root conda env so many times I'd love to know the best way
to do this...

Chris

[Carter Sanders]

Thanks so much for telling me about that. Michael, did you see these issues
even when the jobs worked in different conda envs?

We run this exact scheme with a single builder executing multiple builds
simultaneously on our build system. It is fragile. Kale's recommendation
on read-only might help things. We have ultimately found it necessary to
do a clean miniconda install into a temp dir at the start of each build, or
use docker where it is available. Without these steps, we run into
intermittent bizarre issues where one build will have downloaded a file,
another extracts it, and one or both jobs fail because they don't get what
they're expecting.

sudo chmod -R -w /path/to/root
Sent from my iPhone

Post by Chris Withers

You might want to consider locking down the root environment as

read-only.

Post by Chris Withers
What's the recommended way of doing that? I've accidentally installed

crap into my root conda env so many times I'd love to know the best way to
do this...

Post by Chris Withers
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/1E0663CD-9247-4C0F-896F-8251BFFA5377%40anaconda.com
.
For more options, visit https://groups.google.com/a/continuum.io/d/optout
.