Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Boxiang Sun
gitlab-ce
Commits
27067e56
Commit
27067e56
authored
May 21, 2016
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Clarify how the Registry is enabled in Omnibus
parent
e9817f21
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
10 additions
and
7 deletions
+10
-7
doc/administration/container_registry.md
doc/administration/container_registry.md
+10
-7
No files found.
doc/administration/container_registry.md
View file @
27067e56
...
...
@@ -34,14 +34,17 @@ You can read more about Docker Registry at https://docs.docker.com/registry/intr
If you are using Omnibus, you have to bare in mind the following:
-
The container Registry will be enabled by default if GitLab is configured
with HTTPS and it will listen on port
`5005`
. If you want the Registry to
listen on a port other than
`5005`
, read
[
#Container Registry under existing GitLab domain
](
#container-registry-under-existing-gitlab-domain
)
with HTTPS in new and existing installations (no action is required from the
administrator), and it will listen on port
`5005`
. If you wish to change it,
read
[
#Container Registry under existing GitLab domain
](
#container-registry-under-existing-gitlab-domain
)
on how to achieve that. You will also have to configure your firewall to allow
connections to that port.
-
The container Registry works under HTTPS by default. Using HTTP is possible
but not recommended and out of the scope of this document.
[
See the insecure Registry documentation
][
docker-insecure
]
if you want to
implement this.
incoming connections to that port.
>**Note:**
The container Registry works under HTTPS by default. Using HTTP is possible
but not recommended and out of the scope of this document.
Read the
[
insecure Registry documentation
][
docker-insecure
]
if you want to
implement this.
---
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment