Docker registry ui cannot reach private docker registry V2

Docker Engine
1

Hi all,

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.

curl -v -X GET http://localhost:5000/v2/search

  • Hostname was NOT found in DNS cache
  • Trying 127.0.0.1…
  • Connected to localhost (127.0.0.1) port 5000 (#0)

GET /v2/search HTTP/1.1
User-Agent: curl/7.35.0
Host: localhost:5000
Accept: /

< HTTP/1.1 404 Not Found
< Content-Type: text/plain; charset=utf-8
< Docker-Distribution-Api-Version: registry/2.0
< Date: Fri, 17 Jul 2015 19:13:45 GMT
< Content-Length: 19
<
404 page not found

  • Connection #0 to host localhost left intact

Is there another setting I have to configure before my UI can see the existing registry?

Thanks in advance

2

enter link description herev2 API is different … see doc

check if curl -v http://localhost:5000/v2/ returns correctly an empty JSON

3

Thanks, it returns:
$ curl -v http://localhost:5000/v2/

  • Hostname was NOT found in DNS cache
  • Trying 127.0.0.1…
  • Connected to localhost (127.0.0.1) port 5000 (#0)

GET /v2/ HTTP/1.1
User-Agent: curl/7.35.0
Host: localhost:5000
Accept: /

< HTTP/1.1 200 OK
< Content-Length: 2
< Content-Type: application/json; charset=utf-8
< Docker-Distribution-Api-Version: registry/2.0
< Date: Mon, 20 Jul 2015 21:05:58 GMT
<

  • Connection #0 to host localhost left intact

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?

Thanks

4

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 …

5

erwin16,

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.

Thanks in advance

6

I am looking at ( looks promising…)

it seems that Konrad is working on making his ui V2 compatible

erwin

1 Like
7

Work in progress but SUSE is also doing a registry V2 Frontend https://github.com/SUSE/Portus

8

yes , I’m also tracking it … thanks

9

Great, thanks I’ll check out Panamax. Please keep me posted if you find a good API to manage the registry.

10

Hi again,

Has anyone tried any of the options mentioned above? Which one do you recommend?

Thanks

11

Hi everybody.

I have done many researches on Google in order to solve my following problem.

ErrorServerAccess
ErrorServerAccess.PNG1466×137 26.4 KB

I can not access https://registry-1.docker.io/v2/
I get the following error

code “UNAUTHORIZED”
message “authentication required”
detail:

I don’t know how to solve my problem.

Thank you for your help

Regards.