diff options
author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-11-01 15:11:57 +0300 |
---|---|---|
committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-11-01 15:11:57 +0300 |
commit | 0a0c5aaca5d1ce5403034cb234311518109a0c30 (patch) | |
tree | a0819642b79014566f20bfdd0936bdbb6ee83e21 /doc/api | |
parent | 45ec210a8038cd3ade51bb29018c5805a3f6fae5 (diff) |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/api')
-rw-r--r-- | doc/api/container_registry.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/api/container_registry.md b/doc/api/container_registry.md index 2af725ecdad..c44d800d39f 100644 --- a/doc/api/container_registry.md +++ b/doc/api/container_registry.md @@ -425,7 +425,7 @@ curl --request DELETE --data-urlencode 'name_regex_delete=dev-.+' \ Beside the group- and project-specific GitLab APIs explained above, the Container Registry has its own endpoints. To query those, follow the Registry's built-in mechanism to obtain and use an -[authentication token](https://docs.docker.com/registry/spec/auth/token/). +[authentication token](https://distribution.github.io/distribution/spec/auth/token/). NOTE: These are different from project or personal access tokens in the GitLab application. @@ -436,7 +436,7 @@ These are different from project or personal access tokens in the GitLab applica GET ${CI_SERVER_URL}/jwt/auth?service=container_registry&scope=* ``` -You must specify the correct [scopes and actions](https://docs.docker.com/registry/spec/auth/scope/) to retrieve a valid token: +You must specify the correct [scopes and actions](https://distribution.github.io/distribution/spec/auth/scope/) to retrieve a valid token: ```shell $ SCOPE="repository:${CI_REGISTRY_IMAGE}:delete" #or push,pull |