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
869bce99
Commit
869bce99
authored
Aug 21, 2019
by
Marcel Amirault
Committed by
Achilleas Pipinellis
Aug 21, 2019
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update container_registry.md to handle CA Bundle certs and validation
parent
96629402
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
0 deletions
+9
-0
doc/administration/container_registry.md
doc/administration/container_registry.md
+9
-0
No files found.
doc/administration/container_registry.md
View file @
869bce99
...
@@ -137,6 +137,15 @@ otherwise you will run into conflicts.
...
@@ -137,6 +137,15 @@ otherwise you will run into conflicts.
1.
Save the file and
[
reconfigure GitLab
][]
for the changes to take effect.
1.
Save the file and
[
reconfigure GitLab
][]
for the changes to take effect.
1.
Validate using:
```
sh
openssl s_client
-showcerts
-servername
gitlab.example.com
-connect
gitlab.example.com:443
>
cacert.pem
```
NOTE:
**Note:**
If your certificate provider provides the CA Bundle certificates, append them to the TLS certificate file.
**Installations from source**
**Installations from source**
1.
Open
`/home/git/gitlab/config/gitlab.yml`
, find the
`registry`
entry and
1.
Open
`/home/git/gitlab/config/gitlab.yml`
, find the
`registry`
entry and
...
...
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