kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Merge branch 'docs-remove-DOCKER_AUTH_CONFIG' into 'master' 

Replace the variable DOCKER_AUTH_LOGIN with DOCKER_AUTH_CONFIG

See merge request gitlab-org/gitlab-ce!30339
This commit is contained in:
Achilleas Pipinellis 2019-07-04 09:08:18 +00:00
parent dee95b0d91 aed3fadb55
commit 97b2a3cc7c
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/ci/docker/using_docker_images.md
View File

@ -489,17 +489,17 @@ runtime.
### Using statically-defined credentials
There are two approaches that you can take in order to access a
private registry. Both require setting the environment variable
`DOCKER_AUTH_LOGIN` with appropriate authentication info.
`DOCKER_AUTH_CONFIG` with appropriate authentication info.
1. Per-job: To configure one job to access a private registry, add
`DOCKER_AUTH_LOGIN` as a job variable.
`DOCKER_AUTH_CONFIG` as a job variable.
1. Per-runner: To configure a Runner so all its jobs can access a
private registry, add `DOCKER_AUTH_LOGIN` to the environment in the
private registry, add `DOCKER_AUTH_CONFIG` to the environment in the
Runner's configuration.
See below for examples of each.
#### Determining your `DOCKER_AUTH_LOGIN` data
#### Determining your `DOCKER_AUTH_CONFIG` data
As an example, let's assume that you want to use the `registry.example.com:5000/private/image:latest`
image which is private and requires you to login into a private container registry.