Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
18dddc0c
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
18dddc0c
编写于
5月 13, 2016
作者:
M
Marin Jankovski
提交者:
Achilleas Pipinellis
5月 22, 2016
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Initial docker container registry configuration docs.
上级
529c5821
变更
1
隐藏空白更改
内联
并排
Showing
1 changed file
with
127 addition
and
0 deletion
+127
-0
doc/administration/container_registry.md
doc/administration/container_registry.md
+127
-0
未找到文件。
doc/administration/container_registry.md
0 → 100644
浏览文件 @
18dddc0c
# GitLab Container Registry Administration
Documentation on how to use Container Registry are under
[
TODO
](
TODO.md
)
.
## Configuration
Containers can be large in size and they are stored on the server GitLab is
installed on.
The Container Registry works under HTTPS by default.
This means that the Container Registry requires a SSL certificate.
There are two options on how this can be configured:
1.
Use its own domain - needs a SSL certificate for that specific domain
(eg. registry.example.com) or a wildcard certificate if hosted under a subdomain
(eg. registry.gitlab.example.com)
1.
Use existing GitLab domain and expose the registry on a port - can reuse
existing GitLab SSL certificate
Note that using HTTP is possible,
[
see insecure Registry document.
](
https://github.com/docker/distribution/blob/master/docs/insecure.md
)
Please take this into consideration before configuring Container Registry for
the first time.
## Container Registry under its own domain
Lets assume that you want the Container Registry to be accessible at
`https://registry.gitlab.example.com`
.
### Omnibus GitLab packages
Place your SSL certificate and key in
`/etc/gitlab/ssl/registry.gitlab.example.com.crt`
and
`/etc/gitlab/ssl/registry.gitlab.example.com.key`
and make sure they have
correct permissions:
```
bash
chmod
600 /etc/gitlab/ssl/registry.gitlab.example.com.
*
```
Once the SSL certificate is in place, edit
`/etc/gitlab/gitlab.rb`
with:
```
ruby
registry_external_url
'https://registry.gitlab.example.com'
```
Save the file and
[
reconfigure GitLab
][]
for the changes to take effect.
Users should now be able to login to the Container Registry using:
```
bash
docker login registry.gitlab.example.com
```
with their GitLab credentials.
If you have a
[
wildcard certificate
][]
, you need to specify the path to the
certificate in addition to the URL, in this case
`/etc/gitlab/gitlab.rb`
will
look like:
```
ruby
registry_external_url
'https://registry.gitlab.example.com'
registry_nginx
[
'ssl_certificate'
]
=
"/etc/gitlab/ssl/certificate.pem"
registry_nginx
[
'ssl_certificate_key'
]
=
"/etc/gitlab/ssl/certificate.key"
```
## Container Registry under existing GitLab domain
Lets assume that your GitLab instance is accessible at
`https://gitlab.example.com`
. You can expose the Container Registry under
a separate port.
Lets assume that you've exposed port
`4567`
in your network firewall.
### Omnibus GitLab packages
Your
`/etc/gitlab/gitlab.rb`
should contain the Container Registry URL as
well as the path to the existing SSL certificate and key used by GitLab.
```
ruby
registry_external_url
'https://gitlab.example.com:4567'
## If your SSL certificate is not in /etc/gitlab/ssl/gitlab.example.com.crt
## and key not in /etc/gitlab/ssl/gitlab.example.com.key uncomment the lines
## below
# registry_nginx['ssl_certificate'] = "/path/to/certificate.pem"
# registry_nginx['ssl_certificate_key'] = "/path/to/certificate.key"
```
Save the file and
[
reconfigure GitLab
][]
for the changes to take effect.
Users should now be able to login to the Container Registry using:
```
bash
docker login gitlab.example.com:4567
```
with their GitLab credentials.
## Container Registry storage path
It is possible to change path where containers will be stored by the Container
Registry.
### Omnibus GitLab packages
By default, the path Container Registry is using to store the containers is in
`/var/opt/gitlab/gitlab-rails/shared/registry`
.
This path is accessible to the user running the Container Registry daemon,
user running GitLab and to the user running Nginx web server.
In
`/etc/gitlab/gitlab.rb`
:
```
ruby
gitlab_rails
[
'registry_path'
]
=
"/path/to/registry/storage"
```
Save the file and
[
reconfigure GitLab
][]
for the changes to take effect.
**NOTE**
You should confirm that the GitLab, registry and the web server user
have access to this directory.
[
reconfigure gitlab
]:
../../administration/restart_gitlab.md
"How to restart GitLab documentation"
[
wildcard certificate
]:
"https://en.wikipedia.org/wiki/Wildcard_certificate"
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录