Kaynağa Gözat

Merge pull request #6835 from OddBloke/master

Explain ADD invalidation more accurately
James Turnbull 11 yıl önce
ebeveyn
işleme
037a869919
1 değiştirilmiş dosya ile 7 ekleme ve 3 silme
  1. 7 3
      docs/sources/reference/builder.md

+ 7 - 3
docs/sources/reference/builder.md

@@ -169,9 +169,8 @@ will be reused during the next build.
 The cache for `RUN` instructions can be invalidated by using the `--no-cache`
 flag, for example `docker build --no-cache`.
 
-The first encountered `ADD` instruction will invalidate the cache for all
-following instructions from the 'Dockerfile' if the contents of the context
-have changed. This will also invalidate the cache for `RUN` instructions.
+The cache for `RUN` instructions can be invalidated by `ADD` instructions. See
+[below](#add) for details.
 
 ### Known Issues (RUN)
 
@@ -285,6 +284,11 @@ In the case where `<src>` is a remote file URL, the destination will have permis
 > or use another tool from within the container as ADD does not support
 > authentication.
 
+> **Note**:
+> The first encountered `ADD` instruction will invalidate the cache for all
+> following instructions from the Dockerfile if the contents of `<src>` have
+> changed. This includes invalidating the cache for `RUN` instructions.
+
 The copy obeys the following rules:
 
 - The `<src>` path must be inside the *context* of the build;