vbatts/registry
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Added Nginx Recipe Redirect

Browse source
This commit is contained in:
ollypom 2020-01-10 12:39:40 +00:00
parent f580993c80
commit fdb1abd387
1 changed files with 4 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
docs/recipes/nginx.md
View file

@ -2,6 +2,8 @@
description: Restricting access to your registry using a nginx proxy description: Restricting access to your registry using a nginx proxy
keywords: registry, on-prem, images, tags, repository, distribution, nginx, proxy, authentication, TLS, recipe, advanced keywords: registry, on-prem, images, tags, repository, distribution, nginx, proxy, authentication, TLS, recipe, advanced
title: Authenticate proxy with nginx title: Authenticate proxy with nginx
redirect_from:
- /registry/nginx/
--- ---
## Use-case ## Use-case
@ -40,8 +42,8 @@ proxy itself.
> **Note**: Docker does not recommend binding your registry to `localhost:5000` without > **Note**: Docker does not recommend binding your registry to `localhost:5000` without
> authentication. This creates a potential loophole in your Docker Registry security. > authentication. This creates a potential loophole in your Docker Registry security.
> As a result, anyone who can log on to the server where your Docker Registry is running > As a result, anyone who can log on to the server where your Docker Registry is running
> can push images without authentication. > can push images without authentication.
Furthermore, introducing an extra http layer in your communication pipeline Furthermore, introducing an extra http layer in your communication pipeline
makes it more complex to deploy, maintain, and debug. Make sure the extra makes it more complex to deploy, maintain, and debug. Make sure the extra