I am running a private docker registry: docker run -d -e SEARCH_BACKEND=SQLAlchemy -p 5000:5000 registry:2
I am also running a Docker registry UI on the same host: docker run -p 80:8080 -it -e APP_CONTEXT=ui -e REG1=http://172.17.42.1:5000/v1/ atcol/docker-registry-ui
But the UI cannot find the registry on port 5000. Curl returns 404 page not found and I cannot access 172.17.42.1:5000 and localhost:5000 via the browser either.
I have the registry:2 docker container running, and at the same time I have the registry-ui docker container running, too. The problem is I can’t add my registry:2 as a new registry inside the UI. I just like to be able to use the UI to access my registry:2 docker container, is that even possible? if so, please let me know how?
good … your docker registry seems to run correctly…
I also tried to use the latest docker-ui without any success it was designed for V1 … and should be updated to run with v2… check issues on github for the docker-ui … it may not be ready for V2…
I gave up using it … I’m working on using another docker-ui ( Rails version ) which seems to be ready for v2… currently I’m trying to set up S3 storage for my V2 registry … few examples available so it takes time …
Thanks for your reply. Can you post a link to the UI you are currently using? Is that ready for V2? I have no luck with the docker-ui. All I need is to have a API to manage my registry.