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
1
Merge Requests
1
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
nexedi
gitlab-ce
Commits
db205ab6
Commit
db205ab6
authored
Jun 24, 2020
by
GitLab Bot
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add latest changes from gitlab-org/gitlab@12-10-stable-ee
parent
62a9b70c
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
8 additions
and
8 deletions
+8
-8
doc/administration/packages/container_registry.md
doc/administration/packages/container_registry.md
+8
-8
No files found.
doc/administration/packages/container_registry.md
View file @
db205ab6
...
...
@@ -110,7 +110,7 @@ expose the Registry on a port so that you can reuse the existing GitLab TLS
certificate.
Assuming that the GitLab domain is
`https://gitlab.example.com`
and the port the
Registry is exposed to the outside world is
`
4567
`
, here is what you need to set
Registry is exposed to the outside world is
`
5050
`
, here is what you need to set
in
`gitlab.rb`
or
`gitlab.yml`
if you are using Omnibus GitLab or installed
GitLab from source respectively.
...
...
@@ -124,7 +124,7 @@ otherwise you will run into conflicts.
path to the existing TLS certificate and key used by GitLab:
```
ruby
registry_external_url
'https://gitlab.example.com:
4567
'
registry_external_url
'https://gitlab.example.com:
5050
'
```
Note how the
`registry_external_url`
is listening on HTTPS under the
...
...
@@ -145,7 +145,7 @@ otherwise you will run into conflicts.
1.
Validate using:
```
shell
openssl s_client
-showcerts
-servername
gitlab.example.com
-connect
gitlab.example.com:
443
>
cacert.pem
openssl s_client
-showcerts
-servername
gitlab.example.com
-connect
gitlab.example.com:
5050
>
cacert.pem
```
NOTE:
**Note:**
...
...
@@ -160,7 +160,7 @@ If your certificate provider provides the CA Bundle certificates, append them to
registry
:
enabled
:
true
host
:
gitlab.example.com
port
:
4567
port
:
5050
```
1.
Save the file and
[
restart GitLab
](
../restart_gitlab.md#installations-from-source
)
for the changes to take effect.
...
...
@@ -170,7 +170,7 @@ Users should now be able to login to the Container Registry with their GitLab
credentials using:
```
shell
docker login gitlab.example.com:
4567
docker login gitlab.example.com:
5050
```
### Configure Container Registry under its own domain
...
...
@@ -1056,7 +1056,7 @@ A user attempted to enable an S3-backed Registry. The `docker login` step went
fine. However, when pushing an image, the output showed:
```
plaintext
The push refers to a repository [s3-testing.myregistry.com:
4567
/root/docker-test/docker-image]
The push refers to a repository [s3-testing.myregistry.com:
5050
/root/docker-test/docker-image]
dc5e59c14160: Pushing [==================================================>] 14.85 kB
03c20c1a019a: Pushing [==================================================>] 2.048 kB
a08f14ef632e: Pushing [==================================================>] 2.048 kB
...
...
@@ -1148,8 +1148,8 @@ Now that we have mitmproxy and Docker running, we can attempt to login and push
a container image. You may need to run as root to do this. For example:
```
shell
docker login s3-testing.myregistry.com:
4567
docker push s3-testing.myregistry.com:
4567
/root/docker-test/docker-image
docker login s3-testing.myregistry.com:
5050
docker push s3-testing.myregistry.com:
5050
/root/docker-test/docker-image
```
In the example above, we see the following trace on the mitmproxy window:
...
...
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