summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFederico <federicober@users.noreply.github.com>2022-07-18 17:32:52 +0200
committerGitHub <noreply@github.com>2022-07-18 17:32:52 +0200
commitfcda0edff5e86f1f481115774a230245800b65a4 (patch)
tree75b5610784dcd48884bf6b35cffedc25ff43b2f4
parentc9cb7f4629bdd8c61b792feff6dacb1d2e848d57 (diff)
downloadpip-fcda0edff5e86f1f481115774a230245800b65a4.tar.gz
Suggest disabling pip cache in containers
When building containers (like docker or podman) the layer system already handles the caching. Not disabling pip's cache could result in the duplication of the size of the images. I know this sujbject is not specially relevant to the documentation, so the comment is fairly small. Duplication of pip's cache is a recurrent problem in many Python images
-rw-r--r--docs/html/topics/caching.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/html/topics/caching.md b/docs/html/topics/caching.md
index 929ac3541..08e4acba3 100644
--- a/docs/html/topics/caching.md
+++ b/docs/html/topics/caching.md
@@ -140,6 +140,6 @@ The {ref}`pip cache` command can be used to manage pip's cache.
pip's caching behaviour is disabled by passing the `--no-cache-dir` option.
-It is, however, recommended to **NOT** disable pip's caching. Doing so can
+It is, however, recommended to **NOT** disable pip's caching (except for building containerized appplications). Doing so can
significantly slow down pip (due to repeated operations and package builds)
and result in significantly more network usage.