-
Notifications
You must be signed in to change notification settings - Fork 612
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Repositories are not showing up #170
Comments
I just found the logs :-)
Looks like the frontend cannot reach the backend - no idea why :-( Selinux is set to permissive by the way |
Argh - got it :-) Actually pointing to the registry with localhost does not seem to be so clever. Fixed by linking the registry to the frontend and referring to ENV_DOCKER_REGISTRY_HOST=registry instead of ENV_DOCKER_REGISTRY_HOST=localhost finally let my repository appear :-)
|
Hi,
I am trying to setup a custom docker registry server and would also like to access the content of the registry via browser. First I stumbled upon Philipp Wintermantel´s Blog and from there I followed the link to this project. The core registry is up and running so far but I was neither able to get the frontend part running from Philipp´s blog nor from the example-setup here.
The frontend actually starts but when I push for example the busybox image to the registry it will not show up in the frontend.
I double checked by connecting to the registry container having a look in the registry storage location:
I started the registry like this:
[centos-linux-7 ~]# docker run -d --name registry -p 5000:5000 -e SEARCH_BACKEND=sqlalchemy -e STORAGE_PATH=/registry registry
and the frontend like this:
[centos-linux-7 ~]# docker run -d --name registry-frontend -e ENV_DOCKER_REGISTRY_HOST=localhost -e ENV_DOCKER_REGISTRY_PORT=5000 -p 8080:80 konradkleine/docker-registry-frontend:v2
The only thing I wonder is why the actual storage path from the config.yml
/var/lib/registry
expands to
/var/lib/registry/docker/registry
in the container. Does this maybe point to a misconfiguration or incompatibility somehow?
I am running:
on
docker-registry-frontend version:
I hope that someone can point me to the right direction. Any hint would be very much appreciated.
Best regards,
Christian
The text was updated successfully, but these errors were encountered: