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
Léo-Paul Géneau
gitlab-ce
Commits
427e651c
Commit
427e651c
authored
Jun 03, 2019
by
Ray Paik
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'patch-48' into 'master'
Docs: Fix typos See merge request gitlab-org/gitlab-ce!29020
parents
342992cd
a5b6a18d
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/user/project/container_registry.md
doc/user/project/container_registry.md
+2
-2
No files found.
doc/user/project/container_registry.md
View file @
427e651c
...
@@ -53,7 +53,7 @@ If you visit the **Registry** link under your project's menu, you can see the
...
@@ -53,7 +53,7 @@ If you visit the **Registry** link under your project's menu, you can see the
explicit instructions to login to the Container Registry using your GitLab
explicit instructions to login to the Container Registry using your GitLab
credentials.
credentials.
For example if the Registry's URL is
`registry.example.com`
, the you should be
For example if the Registry's URL is
`registry.example.com`
, the
n
you should be
able to login with:
able to login with:
```
```
...
@@ -204,7 +204,7 @@ at the communication between the client and the Registry.
...
@@ -204,7 +204,7 @@ at the communication between the client and the Registry.
The REST API between the Docker client and Registry is
[
described
The REST API between the Docker client and Registry is
[
described
here
](
https://docs.docker.com/registry/spec/api/
)
. Normally, one would just
here
](
https://docs.docker.com/registry/spec/api/
)
. Normally, one would just
use Wireshark or tcpdump to capture the traffic and see where things went
use Wireshark or tcpdump to capture the traffic and see where things went
wrong. However, since all communication between Docker clients and servers
wrong. However, since all communication
s
between Docker clients and servers
are done over HTTPS, it's a bit difficult to decrypt the traffic quickly even
are done over HTTPS, it's a bit difficult to decrypt the traffic quickly even
if you know the private key. What can we do instead?
if you know the private key. What can we do instead?
...
...
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