Anaconda writes at ~/.conda
Open
Nobody has claimed this yet.
bug
triage
- Dominant language
- Python
- Stars
- 5.1k
- Forks
- 2.5k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 82
Description
Steps to reproduce
spack install anaconda3@2023.09-0
This will try to write in my home directory. I use a bwrap wrapper that allows me to contain such unwanted behaviors. This makes anaconda install fail.
I would expect that all the places that spack writes to are well-defined. This .conda access is violating that assumption.
Error message
Extracting : sphinxcontrib-qthelp-1.0.3-pyhd3eb1b0_0.tar.bz2: 100%|█████████▉| 516/517 [02:07<00:00, 2.79it/s]
mkdir: cannot create directory '.../myhome/.conda': Read-only file system
Information on your system
$ spack debug report
* **Spack:** 0.24.0.dev0 (b88b842455ebaaa9a4f24a6bbea62bb862ff9b11)
* **Python:** 3.6.8
* **Platform:** linux-rhel8-zen4
General information
- I have run
spack debug reportand reported the version of Spack/Python/Platform - I have searched the issues of this repo and believe this is not a duplicate
- I have run the failing commands in debug mode and reported the output
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with spack install anaconda3@2023.09-0 and trace how the Anaconda installation handles its home-directory paths. Check which configured or temporary locations are used during extraction; done means the install no longer writes to ~/.conda and succeeds with a read-only home directory.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- anaconda, python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100