Commit b03f1699 authored by Grzegorz Bizon's avatar Grzegorz Bizon

Extend registry docs regarding multi-level repositories

parent 33329d40
...@@ -10,7 +10,7 @@ ...@@ -10,7 +10,7 @@
- Starting from GitLab 8.12, if you have 2FA enabled in your account, you need - Starting from GitLab 8.12, if you have 2FA enabled in your account, you need
to pass a personal access token instead of your password in order to login to to pass a personal access token instead of your password in order to login to
GitLab's Container Registry. GitLab's Container Registry.
- Multiple level image names support was added in GitLab 8.15 - Multiple level image names support was added in GitLab 9.1
With the Docker Container Registry integrated into GitLab, every project can With the Docker Container Registry integrated into GitLab, every project can
have its own space to store its Docker images. have its own space to store its Docker images.
...@@ -65,6 +65,16 @@ Your image will be named after the following scheme: ...@@ -65,6 +65,16 @@ Your image will be named after the following scheme:
<registry URL>/<namespace>/<project>/<image> <registry URL>/<namespace>/<project>/<image>
``` ```
GitLab supports up to three levels of image repository names.
Following image repository names are valid:
```
registry.example.com/<namespace>/<project>
registry.example.com/<namespace>/<project>/image
registry.example.com/<namespace>/<project>/image/type
```
## Use images from GitLab Container Registry ## Use images from GitLab Container Registry
To download and run a container from images hosted in GitLab Container Registry, To download and run a container from images hosted in GitLab Container Registry,
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment