From ed868b96bd97f71879ea1d4a9f8b4b12f2d6c39f Mon Sep 17 00:00:00 2001 From: Thomas Date: Tue, 20 Aug 2024 16:47:16 +0200 Subject: [PATCH] 2nd conda export variant (#171) --- bih-cluster/docs/storage/migration-faq.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/bih-cluster/docs/storage/migration-faq.md b/bih-cluster/docs/storage/migration-faq.md index da17c9ce2..f1f3aa4f3 100644 --- a/bih-cluster/docs/storage/migration-faq.md +++ b/bih-cluster/docs/storage/migration-faq.md @@ -64,6 +64,8 @@ done ``` If you run into errors it might be better to use `conda env export -n $env --no-builds -f $env.yaml`. + In case your old conda installation cannot be activated anymore, you can also use your new conda to do the export + by specifying a full path like so: `conda env export -p /fast/work/user/$USER/miniconda/envs/ -f .yaml`. 3. Install a fresh version of conda or mamba in your new work folder. Don't forget to turn off automatic base environment activation for less delay during login and reduced strain on the login nodes.