Browse and modify your Docker registry in a browser.
Find a file
2014-09-30 17:13:27 +02:00
app Better HTML title rendering 2014-09-30 12:31:19 +02:00
screenshots Added screenshots 2014-09-30 16:58:31 +02:00
test Initial commit after: yo angular && npm install 2014-09-12 13:51:09 +02:00
.bowerrc Initial commit after: yo angular && npm install 2014-09-12 13:51:09 +02:00
.dockerignore Added screenshots 2014-09-30 16:58:31 +02:00
.editorconfig Initial commit after: yo angular && npm install 2014-09-12 13:51:09 +02:00
.gitattributes Initial commit after: yo angular && npm install 2014-09-12 13:51:09 +02:00
.gitignore Ignore *.swp files 2014-09-15 16:16:24 +02:00
.jshintrc Initial commit after: yo angular && npm install 2014-09-12 13:51:09 +02:00
.travis.yml Initial commit after: yo angular && npm install 2014-09-12 13:51:09 +02:00
apache-site.conf Replaced NGINX with Apache for Kerberos auth. SSL is working. 2014-09-29 14:05:02 +02:00
bower.json Add angular-bootstrap for tabset directive. Add loading bar for all XHR requests. 2014-09-29 12:28:07 +02:00
Dockerfile This should resolve #1 2014-09-30 16:04:40 +02:00
Gruntfile.js Respect HTML files in scripts/directives/ folders 2014-09-17 15:30:04 +02:00
LICENSE Added MIT license 2014-09-17 15:51:16 +02:00
package.json Dev workaround to query registry without CORS. Thanks to grunt proxy /v1 now redirects to path-to-your-registry host. 2014-09-15 09:56:18 +02:00
README.md Update README.md 2014-09-30 17:13:27 +02:00
start-apache.sh Replaced NGINX with Apache for Kerberos auth. SSL is working. 2014-09-29 14:05:02 +02:00

About

The docker-registry-frontend is a pure web-based solution for browsing and modifying any private Docker repository that you can reach via a URL.

Usage

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

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

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

SSL encryption

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

Note that the application still serves the port 80 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 to https://localhost.

Kerberos authentication

If you want to use Kerberos to protect access to the registry frontend, you can do the followiung:

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

You can of course combine SSL and Kerberos.

Features

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

Contributions are welcome!

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.

Thank you for your interest!

-- Konrad