-c anaconda. But we should be unmixing these from anaconda.org/anaconda now I feel (and forcing people who want to use free to add
-c freebecause it's full of less well built software that I personally wouldn't run)
pkgs/freepackages on https://anaconda.org/anaconda are labeled
Argh, I did not pay attention and conda updated python 2->3 in my base environment after doing
conda update -n base --all
Now I am in state where conda is still in
lib/python2.7/conda/..., but the interpreter is python3.7, therefore when calling conda I now get this:
Traceback (most recent call last): File "/usr/users/croth1/miniconda/bin/conda", line 7, in <module> from conda.cli import main ModuleNotFoundError: No module named 'conda'
Any recommendations what's the best way to go from here?
Hi I have a question that I hope someone might be able to help with:
The context is that we have a Zero2Jupyter set up on Kubernettes and our single user docker images are big (6+GB) a large amount of this is a very heavy conda environment. We are really keen to shrink our image sizes.
One idea to do this is to create a docker image with a vanilla miniconda install and create a cloud filesystem with our heavy conda environment (read-only shared across our users) and mount that in at
What I'm not clear on is:
ROOT_DIR/env/my-envour cloud storage?
/pkgsfeels like it is from reading the docs
/pkgsis shared if I did a deep copy (i.e. following softlinks) when creating my shared env might that work?
A lot of questions, your help really appreciate.
conda remove --name myenv --allor
conda env remove --name myenvcan be used to remove an environment. I noticed they don't exactly do the same.
conda remove --allfirst removes all packages before to remove the env.
conda env removedoesn't. Is that historical? Is one way preferred?
conda installyour thing. If it says that it is already satisfied, you can try the