Repository files navigation

Thedocker-registry-frontend is a pure web-based solution for browsing and modifying a private Docker registry.

THIS VERSION OF THE DOCKER REGISTRY FRONTEND ONLY WORKS WITH THE DOCKER REGISTRY V1 API (aka v0.9.1). THERE'S ALSO A"V2" BRANCH WHICH WORKS WITH THE NEWER V2 DOCKER REGISTRY (AKA "DISTRIBUTION"). YOU SHOULD CONSIDER USING THE"V2" BRANCH.

THIS BRANCH IS CONSIDERED DEPRECATED SINCE THE OLD DOCKER REGISTRY ITSELF IS DEPRECATED AS WELL.

TO PULL A VERSION OF THIS BRANCH FROM THE DOCKER HUB, MAKE SURE YOU PULL AND RUNkonradkleine/docker-registry-frontend:v1-deprecated

For a list of all the features, please see theWiki.

To learn how to develop for the docker-registry-frontend, seehere.

This application is available in the form of a Docker image that you can run as a container by executing this command:

sudo docker run \  -d \  -e ENV_DOCKER_REGISTRY_HOST=ENTER-YOUR-REGISTRY-HOST-HERE \  -e ENV_DOCKER_REGISTRY_PORT=ENTER-PORT-TO-YOUR-REGISTRY-HOST-HERE \  -p 8080:80 \  konradkleine/docker-registry-frontend:v1-deprecated

This command starts the container and forwards the container's private port80 to your host's port8080. Make sure you specify the correct url to your registry.

When the application runs you can open your browser and navigate tohttp://localhost:8080.

If the Docker registry is only reachable via HTTPs (e.g. if it sits behind a proxy) , you can run the following command:

sudo docker run \  -d \  -e ENV_DOCKER_REGISTRY_HOST=ENTER-YOUR-REGISTRY-HOST-HERE \  -e ENV_DOCKER_REGISTRY_PORT=ENTER-PORT-TO-YOUR-REGISTRY-HOST-HERE \  -e ENV_DOCKER_REGISTRY_USE_SSL=1 \  -p 8080:80 \  konradkleine/docker-registry-frontend:v1-deprecated

If you want to run the application with SSL enabled, you can do the following:

sudo docker run \  -d \  -e ENV_DOCKER_REGISTRY_HOST=ENTER-YOUR-REGISTRY-HOST-HERE \  -e ENV_DOCKER_REGISTRY_PORT=ENTER-PORT-TO-YOUR-REGISTRY-HOST-HERE \  -e ENV_USE_SSL=yes \  -v $PWD/server.crt:/etc/apache2/server.crt:ro \  -v $PWD/server.key:/etc/apache2/server.key:ro \  -p 443:443 \  konradkleine/docker-registry-frontend:v1-deprecated

Note that the application still serves the port80 but it is simply not exposed ;). Enable it at your own will. When the application runs with SSL you can open your browser and navigate tohttps://localhost.

If you are running the Docker registry on the same host as the application but only accessible to the application (eg. listening on127.0.0.1) then you can use the application as the registry itself.

Normally this would then give bad advice on how to access a tag:

docker pull localhost:5000/yourname/imagename:latest

We can override what hostname and port to put here:

sudo docker run \ -d \ -e ENV_DOCKER_REGISTRY_HOST=localhost \ -e ENV_DOCKER_REGISTRY_PORT=5000 \ -e ENV_REGISTRY_PROXY_FQDN=ENTER-YOUR-APPLICATION-HOST-HERE \ -e ENV_REGISTRY_PROXY_PORT=ENTER-PORT-TO-YOUR-APPLICATION-HOST-HERE \ -e ENV_USE_SSL=yes \ -v $PWD/server.crt:/etc/apache2/server.crt:ro \ -v $PWD/server.key:/etc/apache2/server.key:ro \ -p 443:443 \ konradkleine/docker-registry-frontend:v1-deprecated

A value of80 or443 forENV_REGISTRY_PROXY_PORT will not actually be shown as Docker will check443 and then80 by default.

If you want to use Kerberos to protect access to the registry frontend, you cando the following:

sudo docker run \  -d \  -e ENV_DOCKER_REGISTRY_HOST=ENTER-YOUR-REGISTRY-HOST-HERE \  -e ENV_DOCKER_REGISTRY_PORT=ENTER-PORT-TO-YOUR-REGISTRY-HOST-HERE \  -e ENV_AUTH_USE_KERBEROS=yes \  -e ENV_AUTH_NAME="Kerberos login" \  -e ENV_AUTH_KRB5_KEYTAB=/etc/apache2/krb5.keytab \  -v $PWD/krb5.keytab:/etc/apache2/krb5.keytab:ro \  -e ENV_AUTH_KRB_REALMS="ENTER.YOUR.REALMS.HERE" \  -e ENV_AUTH_KRB_SERVICE_NAME=HTTP \  -p 80:80 \  konradkleine/docker-registry-frontend:v1-deprecated

You can of course combine SSL and Kerberos.

If you want to start applicaton with browse mode which means no repos/tags management feature in the UI, You can specifyENV_MODE_BROWSE_ONLY flag as follows:

sudo docker run \  -d \  -e ENV_DOCKER_REGISTRY_HOST=ENTER-YOUR-REGISTRY-HOST-HERE \  -e ENV_DOCKER_REGISTRY_PORT=ENTER-PORT-TO-YOUR-REGISTRY-HOST-HERE \  -e ENV_MODE_BROWSE_ONLY=true \  -p 8080:80 \  konradkleine/docker-registry-frontend:v1-deprecated

You can settrue orfalse to this flag.

If you like the application, I invite you to contribute and report bugs or feature request on the project's github page:https://github.com/kwk/docker-registry-frontend.To learn how to develop for the docker-registry-frontend, seehere.

Thank you for your interest!

-- Konrad