kwk / docker-registry-frontend

Browse and modify your Docker registry in a browser.
https://registry.hub.docker.com/u/konradkleine/docker-registry-frontend/
MIT License
1.68k stars 616 forks source link

Can not find any repository in main page #181

Open DarrenJiang1990 opened 6 years ago

DarrenJiang1990 commented 6 years ago

A docker private registry has been running in my server with the official registry image(docker.io), it can be visited from other machines by a the URL 192.168.17.129:5000 in HTTP method ,then the docker-registry-frontend was started with the following script: docker run -d -e ENV_DOCKER_REGISTRY_HOST=192.168.17.129 -e ENV_DOCKER_REGISTRY_PORT=5000 -p 8080:80 konradkleine/docker-registry-frontend:v2

At last,when i visited the main page of docker-registry-frontend ---http://192.168.17.129:8080/repositories/20 ,no any repository was shown in the web page,some errors appeared in the console of my chrome browser , a picture will be provided in the following text。

error

How can i solve the problem

By the way,the server OS is Centos 7.2,the version of docker is 1.12.6,and the registry is docker.io/registry:latest, expect helpful replies!

DarrenJiang1990 commented 6 years ago

how can i solve the problem

DarrenJiang1990 commented 6 years ago

I found the problem that the docker-registry-frontend container could not visit the register container in a same machine for the reason a error “No route to host” occurred when I executed the following goal in the docker-registry-frontend container: curl http://192.168.17.129:5000/v2/_catalog

So I realized the real cause is that the register container could not connect by the the docker-registry-frontend container via network even though those two containers were in a same one machine,then I solved the problem with the following running command by a method of container link:

docker run -d -e ENV_DOCKER_REGISTRY_HOST=registry -e ENV_DOCKER_REGISTRY_PORT=5000 -p 8080:80 --link registry:registry konradkleine/docker-registry-frontend:v2 Thanks all !

artemkamolodets commented 6 years ago

I have the same issue. The registry is working as well, but frontend can't see any images thet i've pushed in (they are presented in the filesystem structure of the registry container). I've got the following error: 1 Here is my compose file: 2 3

javydreamercsw commented 6 years ago

Doesn't work for me. I keep getting HTTPS: disabled connection for (registry). Any hints?

samdra9on commented 6 years ago

Try to use the the IP address of the host machine in the following command: docker run -d -e ENV_DOCKER_REGISTRY_HOST=<**Host Machine's IP**> -e ENV_DOCKER_REGISTRY_PORT=5000 -p 8080:80 konradkleine/docker-registry-frontend:v2 It works for me. image

ryanrca commented 5 years ago

Using the IP address vs. the hostname fixed this problem for me.

ssolipuramwex commented 5 years ago

I am using Azure Container registry as my private docker registry. When running the container I specifed the host and port number of the Azure container registry. Where do I specify the container registry credentials when running this docker image? I only see a home page with empty repositories. Any help is greatly appreciated