CATALOG_NOT_FOUND with configuration nearly identical to example about docker-registry-ui

[evonicgu]

Sorry for late response, everything turned out to be fine back then. I just had to wait for like 5-10 minutes and it started working. Idk how, because nothing was changed

[evonicgu]

It is also important to add, that when I try pinging registry-server:5000 using the sudo docker exec -i registry-ui /bin/sh everything works fine, pings go all the way through, but it is always not found in the browser and the logs do not show registry-server anywhere

[evonicgu]

But, although it is pingable, the status code from curl http://localhost:5000/_catalog?n=1000 or curl http://registry-server:5000/_catalog?n=1000 (this one being from the registry-ui container) is always 404, which it should not be

[evonicgu]

I do not know why is the UI trying to use registry v1 paths, because curl http://localhost:5000/v2/_catalog?n=1000 does perfectly fine

[Joxit]

Hello,
Please the next time use the issues templates I made will all the fields completed.

Since you're using NGINX_PROXY_PASS_URL what's the result of curl http://registry-server:9090/v2/_catalog?n=1000 ?

When you're using NGINX_PROXY_PASS_URL, the option REGISTRY_URL must stay unset.