Added Nginx Recipe Redirect
							parent
							
								
									f580993c80
								
							
						
					
					
						commit
						fdb1abd387
					
				|  | @ -2,6 +2,8 @@ | |||
| description: Restricting access to your registry using a nginx proxy | ||||
| keywords: registry, on-prem, images, tags, repository, distribution, nginx, proxy, authentication, TLS, recipe, advanced | ||||
| title: Authenticate proxy with nginx | ||||
| redirect_from: | ||||
| - /registry/nginx/ | ||||
| --- | ||||
| 
 | ||||
| ## Use-case | ||||
|  | @ -40,8 +42,8 @@ proxy itself. | |||
| 
 | ||||
| > **Note**: Docker does not recommend binding your registry to `localhost:5000` without | ||||
| > 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  | ||||
| > can push images without authentication.  | ||||
| > As a result, anyone who can log on to the server where your Docker Registry is running | ||||
| > can push images without authentication. | ||||
| 
 | ||||
| Furthermore, introducing an extra http layer in your communication pipeline | ||||
| makes it more complex to deploy, maintain, and debug. Make sure the extra | ||||
|  |  | |||
		Loading…
	
		Reference in New Issue