BCDA-APS / bluesky_training

Bluesky training, including instrument package
https://bcda-aps.github.io/bluesky_training/
Other
11 stars 0 forks source link

DOC: note this is not a bug #154

Open prjemian opened 1 year ago

prjemian commented 1 year ago

During creation of a new custom conda environment, errors such as the ones below, are shown:

(base) jemian@otz ~/.../BCDA-APS/bluesky_training $ cd bluesky/environments/
(base) jemian@otz ~/.../bluesky/environments $ conda env create --force -n bluesky_2023_2 -f ./environment_2023_2.yml --solver=libmamba
Retrieving notices: ...working... done
error    libmamba Could not open lockfile '/APSshare/miniconda/x86_64/pkgs/cache/cache.lock'
error    libmamba Could not open lockfile '/APSshare/miniconda/x86_64/pkgs/cache/cache.lock'
error    libmamba Could not open lockfile '/APSshare/miniconda/x86_64/pkgs/cache/cache.lock'
error    libmamba Could not open lockfile '/APSshare/miniconda/x86_64/pkgs/cache/cache.lock'
apsu/linux-64                                        8.2kB @  34.2kB/s  0.2s
aps-anl-tag/linux-64                                          No change

These are not errors of any problem for the user. The conda environment creation process continues and finds a different directory in which the user does have write permission. Rather, they are actually notices that the user does not have write permission to the drive where the conda base environment is located. This is expected and normal procedure for conda environments in user accounts at the APS. Beam line users do not have write access to /APSshare.

We should provide this additional advice (as details dropdown) in the appropriate section. Or maybe on the FAQ so other sections can reference it.