Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Provide better error information #25
I am using this to connect to a plain vanilla private registry running on
and no information about what could possibly have gone wrong.
I start the UI with:
This is a simple example to verify the registry API is reachable:
This is just a dev instance, so I'm running the registry straight from these Instructions:
Also, as mentioned above, a straight
While I won't argue with your design choices, I would contend that this should be rather unnecessary in a "plain vanilla" dev deployment where one just wishes to see what's possible; especially considering that a plain 'curl' "just works."
And, by the way, thanks for confirming that a better error message would be helpful to everyone
It's really too bad about this: while I have found something "that works," this one seemed to have the promise of a better, more pleasant UI - I guess we'll never know...
CORS (or Cross-origin Resource Sharing) is a browser security and allow by default only Same Origin requests (same URI scheme, host name, and port number). This policy prevents a malicious script on one page from obtaining access to sensitive data on another web page.
If you have the UI on http://localhost/ and registry on http://localhost:5000, without the CORS header your browser will drop the request without notification. That is why
If you don't want to add a configuration file, you can also run your docker registry with the extra option
Anyway, I will add a new proxy config with Nginx, this should fix your issue