Skip to content

revamp "move .conda" page #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
Open

revamp "move .conda" page #129

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
c0153ab
start rewrite relocate software dir
craigsteffen Mar 12, 2025
2047eb7
.conda move to conda clean
craigsteffen Apr 30, 2025
cdc80c7
no move; just conda clean
craigsteffen Apr 30, 2025
b4fd52d
fix code-block
craigsteffen Apr 30, 2025
f7f3a41
fix code: add blank line
craigsteffen Apr 30, 2025
5418567
clean up wording
craigsteffen Apr 30, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
50 changes: 9 additions & 41 deletions docs/source/common/relocate-conda-directory.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,49 +1,17 @@
.. _conda:
.. _dir_full:

Relocating Your .conda Directory to Project Space
Home Directories Full
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Large conda installations may exceed your home directory size. This can be avoided by relocating your ``.conda`` directory to your project space, which has a larger quota than your home directory.
On NCSA systems, users have space in their "home" file system (where their personal configuration files live) and other file systems specific to their work. Quotas on the other file systems are usually much larger. Unfortunately, some software stacks (python and conda in particular) store their libraries and configuration files in a hidden directory in a user's home area. Because home quotas are generally fairly small, it's easy for the software to overrun a user's quota, and then they hit file system quota, which sometimes means they can't even log in.

Relocate your ``.conda`` directory to your project space using the following steps:
We are aware that users are hitting this problem frequently, unfortunately, there's no universal solution. We will populate this page with individual software solutions as we find and test them.

#. Make a ``.conda`` directory in your project space.
Conda
$$$$$$$$$$$$$$$

.. code-block::
Various versions of the conda software can easily fill up user's home quota, especially when the user installs many versions of packages. If you use conda, you can reduce the likelihood of filling up your home directory by frequenty running this command (especially after installing packages):

[testuser1@golubh1 ~]$ mkdir -p /projects/<your proj. dir>/<your username>/.conda
.. code-block::

#. Copy over your existing ``.conda`` data. (This may take several minutes if your ``.conda`` directory is large.)

.. code-block::

[testuser1@golubh1 ~]$ rsync -aAvP ~/.conda/* /projects/<your proj. dir>/<your username>/.conda/

#. Remove your current ``.conda`` directory.

.. code-block::

[testuser1@golubh1 ~]$ rm -rf ~/.conda

#. Create a link to your new ``.conda`` directory.

.. code-block::

[testuser1@golubh1 ~]$ ln -s /projects/<your proj. dir>/<your username>/.conda ~/.conda

|

..
.. code-block::

## Make a .conda dir for yourself in your project space
[testuser1@golubh1 ~]$ mkdir -p /projects/<your proj. dir>/<your username>/.conda

## Copy over existing .conda data
[testuser1@golubh1 ~]$ rsync -aAvP ~/.conda/* /projects/<your proj. dir>/<your username>/.conda/

## Remove your current .conda dir
[testuser1@golubh1 ~]$ rm -rf ~/.conda

## Create link to your new .conda dir
[testuser1@golubh1 ~]$ ln -s /projects/<your proj. dir>/<your username>/.conda ~/.conda
conda clean -a