Repository list fails to load
See original GitHub issueHi,
I’ve just thrown up an instance of this but it doesn’t appear to be working… I’m running the registry frontend on the same host as the registry on port 5000, and launching with:
docker run -d -e ENV_DOCKER_REGISTRY_HOST=fqdn.of.docker.host -e ENV_DOCKER_REGISTRY_PORT=5000 -p 9001:80 --name registryui konradkleine/docker-registry-frontend:v2
The repository load times out. I’m seeing the following error in the response to _catalog?n=20&last=
(html formatting removed):
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request GET /v2/_catalog
Reason: Error reading from remote server
Any ideas? Unsure how to diagnose.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:2
- Comments:10
Top Results From Across the Web
Heatmap loads forever + Repository list fails to load entirely
Heatmap and repository list does not load, at all. Restarting Gitea or anything like that did not work. Error occured after upgrading from ......
Read more >"Failed to export repository list from registry" when ... - ERROR
To export a repository list from the registry, login to the Windows Client machine as a local Administrator user, then run Repository Manager...
Read more >How do I restore the default repositories? - Ask Ubuntu
You can use this trick. Open a terminal ( Pressing Ctrl + Alt + T ) and do these. Move the corrupted one...
Read more >How to fix the repository is not signed error on Ubuntu 20.04
To achieve this, launch the 'Software and Updates' tool as shown. On the 'Software & Updates' window, click on the 'Other Software' tab....
Read more >How to Fix Repository Update Error on Raspberry Pi - Linux Hint
You can fix the repository update error on Raspberry Pi by removing the erroneous repository from the source list using the rm command....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I found the solution : ENV_DOCKER_REGISTRY_USE_SSL=1 needs to be added to the command
tks @lordzuko. Not using it right now, but will give it a try if I do need it…