Users accessing the Dependency Proxy with a personal access token or username and password must A group deploy token with the scope set to read_registry and write_registry.A personal access token with the scope set to read_registry and write_registry.Authenticate with the Dependency Proxyĭocker login -username my_username -password my_password Your images must be stored on Docker Hub.You can use GitLab as a source for your Docker images. Use the Dependency Proxy for Docker images The Dependency Proxy is not available for projects. On the left sidebar, select Packages and registries > Dependency Proxy.Only an administrator canįor the entire GitLab instance. This setting only affects the Dependency Proxy for a group. To enable the proxy, turn on Enable Proxy.On the left sidebar, select Settings > Packages and registries.On the top bar, select Main menu > Groups and find your group.To enable or turn off the Dependency Proxy for a group: Enable or turn off the Dependency Proxy for a group Image/Package GitLab version Docker 11.11+įor a list of planned additions, view theĭirection page. The following images and packages are supported. It’s enabled by default,īut administrators can turn it off. To use the Dependency Proxy, it must be enabled for the GitLab instance. Upstream image from a registry, acting as a pull-through cache. In the case of CI/CD, the Dependency Proxy receives a request and returns the The GitLab Dependency Proxy is a local proxy you can use for your frequently-accessed Introduced support for pull-by-digest and Docker version 20.x in GitLab 13.10.Anonymous access to images in public groups is no longer available starting in GitLab 13.7. Introduced support for private groups in GitLab 13.7.Moved from GitLab Premium to GitLab Free in 13.6.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |