Adds reference to cache dirs which should not be placed inside users home

doc.zih.tu-dresden.de/docs/data_lifecycle/permanent.md

@@ -31,6 +31,20 @@ submit jobs into the batch system. Running jobs are not affected.
      We have no feasible way to get the contribution of
      a single user to a project's disk usage.
 
+Because of the quota, it is recommended not to store cache data, which is automatically
+created by some applications or frameworks, in `/tmp` or in workspaces.
+We cannot list all applications that do this, but some known ones are
+
+| Application      | Environment variable              |
+|:-----------------|:----------------------------------|
+| Singularity      | `SINGULARITY_CACHEDIR`            |
+| pip              | `PIP_CACHE_DIR`                   |
+| Hugging Face      | `HF_HOME` and `TRANSFORMERS_CACHE`|
+| Torch Extensions | `TORCH_EXTENSIONS_DIR`            |
+
+Python virtual environments and conda directories can grow quickly,
+so they should also be placed inside workspaces.
+
 ## Global /projects Filesystem
 
 For project data, we have a global project directory, that allows better collaboration between the