diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2019-09-23 12:06:22 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2019-09-23 12:06:22 +0300 |
| commit | 1d89871c573830a8194110af252e8907177184b3 (patch) | |
| tree | 9aece724c48fc633f38c3b8cbaf2f71fcf4c3f4c /doc/ci/docker | |
| parent | 89861e72b7375353654513aa2bc0a3b60a5e4377 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/docker')
| -rw-r--r-- | doc/ci/docker/using_docker_build.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/ci/docker/using_docker_build.md b/doc/ci/docker/using_docker_build.md index a60ede2c8f8..c87e259aafd 100644 --- a/doc/ci/docker/using_docker_build.md +++ b/doc/ci/docker/using_docker_build.md @@ -526,7 +526,7 @@ Some things you should be aware of: longer, but means you don’t get stuck without security patches to base images. - Doing an explicit `docker pull` before each `docker run` fetches the latest image that was just built. This is especially important if you are - using multiple runners that cache images locally. Using the git SHA in your + using multiple runners that cache images locally. Using the Git SHA in your image tag makes this less necessary since each job will be unique and you shouldn't ever have a stale image. However, it's still possible to have a stale image if you re-build a given commit after a dependency has changed. |