Open kubecto opened 3 months ago
Hi, your issue looks like a docker registry configuration itself, no link with my registry ui.
AFAIK the proxy option for docker registry is meant to be a fallback when the image is not found in your private one.
Please check their documentation: https://distribution.github.io/distribution/about/configuration/#proxy
Hi, I use this docker registry UI and I have an issue...
Bug description
I have deployed a registry+ui mode and set the user login. I can access the http registry ui normally. At this time, it has user login authentication, but I want to configure a cache proxy to automatically log in users and pull the mirror. I hope that the cache proxy can be accessed through the domain name, but after I configure it through nginx, the header of the request forwarding cannot jump to the registry of the central control correctly
1, this is my central terminal registry+ui configuration
my registry config
Startup script
At this point I can normally access my ui page
2、From the proxy cache configuration, I also removed the user authentication, and added the proxy configuration to connect to the central control user name and password
start script
3、from one of my nginx, this nginx I forward to the proxy cache node through the domain name
When I use the nginx domain name to fetch the image, the image cannot be found and I see the error log from registry, http.request.method=HEAD http.request.remoteaddr=10.102.98.22, And 10.102.98.20 was my central control address,
Error message from registry
I also try to
and will proxy_set_header removed, these options are removed, also of no help
Expected behavior
I hope to use the proxy mydown.test.com to pull the mirror from the proxy cache and push the mirror through the central control
System information
-OS: [Centos 7.9]