1berry/docker-cli
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #2192 from mdkalish/patch-1

Browse Source 
Update dead link and add missing info on COPY
This commit is contained in:
Sebastiaan van Stijn 2020-05-01 18:37:02 +02:00 committed by GitHub
commit 80adee0b13
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/reference/builder.md
View File

@ -743,8 +743,7 @@ flag, for example `docker build --no-cache`.
See the [`Dockerfile` Best Practices See the [`Dockerfile` Best Practices
guide](https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/) for more information. guide](https://docs.docker.com/engine/userguide/eng-image/dockerfile_best-practices/) for more information.
The cache for `RUN` instructions can be invalidated by `ADD` instructions. See The cache for `RUN` instructions can be invalidated by [`ADD`](#add) and [`COPY`](#copy) instructions.
[below](#add) for details.
### Known issues (RUN) ### Known issues (RUN)
@ -1114,7 +1113,7 @@ does not support authentication.
> following instructions from the Dockerfile if the contents of `<src>` have > following instructions from the Dockerfile if the contents of `<src>` have
> changed. This includes invalidating the cache for `RUN` instructions. > changed. This includes invalidating the cache for `RUN` instructions.
> See the [`Dockerfile` Best Practices > See the [`Dockerfile` Best Practices
guide](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/) guide – Leverage build cache](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#leverage-build-cache)
> for more information. > for more information.
@ -1303,6 +1302,15 @@ image with the same name is attempted to be used instead.
- If `<dest>` doesn't exist, it is created along with all missing directories - If `<dest>` doesn't exist, it is created along with all missing directories
in its path. in its path.
> **Note**
>
> The first encountered `COPY` 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.
> See the [`Dockerfile` Best Practices
guide – Leverage build cache](https://docs.docker.com/develop/develop-images/dockerfile_best-practices/#leverage-build-cache)
> for more information.
## ENTRYPOINT ## ENTRYPOINT