||2 years ago|
|.github/ISSUE_TEMPLATE||3 years ago|
|bin||2 years ago|
|demo||2 years ago|
|dist||2 years ago|
|examples||2 years ago|
|nginx||2 years ago|
|src||2 years ago|
|.dockerignore||4 years ago|
|.gitignore||3 years ago|
|CODE_OF_CONDUCT.md||4 years ago|
|CONTRIBUTORS.md||2 years ago|
|Dockerfile||4 years ago|
|Dockerfile.static||5 years ago|
|LICENSE||7 years ago|
|README.md||2 years ago|
|_config.yml||3 years ago|
|arm32v7-static.dockerfile||2 years ago|
|arm32v7.dockerfile||5 years ago|
|arm64v8-static.dockerfile||2 years ago|
|arm64v8.dockerfile||5 years ago|
|debian-static.dockerfile||2 years ago|
|debian.dockerfile||5 years ago|
|docker-registry-ui.gif||4 years ago|
|gulpfile.js||2 years ago|
|index.md||4 years ago|
|package.json||2 years ago|
|screenshot.png||4 years ago|
|static.dockerfile||2 years ago|
|Docker Registry User Interface|
Docker Registry UI
This project aims to provide a simple and complete user interface for your private docker registry.
You have the choice between two versions, the standard interface (
joxit/docker-registry-ui:latest) and the static interface (
In the standard interface, there is no default registry, you need to add your own within the UI. With this version, you can manage more than one registry server but all the environment variables will be unavailable. All registries will be stored in the local storage of your browser. No configuration is needed when you launch the UI.
In the static interface, it will connect to a single registry and will not change. The configuration is done at the start of the interface, when you use the docker images whose tags contain the
static keyword. With this version, you can manage only one registry and all environment variables will be available.
This web user interface uses Riot the react-like user interface micro-library and riot-mui components.
Project Page, Live Demo, Examples
- List all your repositories/images.
- List all tags for a image.
- Sort the tag list with number compatibility (see #46).
- Use a secured docker registry.
- Display image size (see #30).
- Multi arch supports, Alpine and Debian based images with supports for arm32v7 and arm64v8.
docker pullcommand to clipboard (see #42).
- Show sha256 for specific tag (hover image tag).
- Display image creation date (see #49)
- Display image history (see #58 & #61).
- Image aggregation (see #56).
- Display image/tag count (see #56 issue comment).
- Select multiple tags to delete (see #29).
- Select all tags with ALT + Click to delete (see #80).
- One interface for many registries standard interface.
- Share your docker registry with query parameter
https://joxit.dev/docker-registry-ui/demo?url=https://registry.example.com) standard interface.
joxit/docker-registry-ui:staticas reverse proxy (with
REGISTRY_URLenvironment variable) to your docker registry (This will avoid CORS) static interface.
- Add Title when using
REGISTRY_URL(see #28) static interface.
- Customise docker pull command on static registry UI (see #71) static interface.
- Add custom header via environment variable and file via
NGINX_PROXY_HEADER_*(see #89) static interface
- Show/Hide content digest in taglist via
SHOW_CONTENT_DIGEST(values are: [
true) (see #126) static interface.
- Limit the number of elements in the image list via
CATALOG_ELEMENTS_LIMIT(see #127) static interface.
- Multi arch support in history page (see #130 and #134)
- What is the difference between
latesttag was the first version of the project, one UI for many docker registries. The
statictag allows you to have an interface for a single registry and also allows you select your features.
- Why, when I delete all tags of an image, the image is still in the UI ?
- This is a limitation of docker registry, the garbage collector don't remove empty images. If you want to delete dangling images, you will need to delete the folder in your registry data. (see #77)
- Why the image size in the UI is not the same as displayed during
- The UI displays the compressed size of the image and not the extracted size version.
- Can I use HTTPS on the UI ?
- Yes, put your favourite reverse proxy on the front of the UI. Your reverse proxy will take care of HTTPS connection.
- Does the UI support authentication ?
- Yes, but it supports only basic auth. It's a simple standalone frontend, it will use your browser window for authentication.
- Can I use the UI and docker client with an insecure registry (registry url without https) ?
- Yes you can, you must first configure your docker client. (see #76)
- What does Mixed Content error mean ?
- This means you are using a UI with HTTPS and your registry is using HTTP (unsecured). When you are on a HTTPS site, you can't get HTTP content. Upgrade you registry with a HTTPS connection.
- Why the default nginx
Hostis set to
- Why DELETE fails with 401 status code (using Basic Auth) ?
- This is caused by a bug in docker registry, I suggest to have your UI on the same domain than your registry e.g. registry.example.com/ui/. (see #104).
- Can I use the docker registry ui as a standalone application (with Electron) ?
- I deleted images through the UI, but they are still present on the server. How can I delete them?
- Why when I delete one tag, all tags with the same SHA are deleted ?
- This a docker registry API limitation, there is only one way to delete images with tag, it's by its
manifest(it's a sha of the content). So when you delete a tag, this will delete all tags of this image with the same SHA/manifest.
- This a docker registry API limitation, there is only one way to delete images with tag, it's by its
Need more informations ? Try my examples or open an issue.
The docker image contains the source code and nginx in order to serve the docker-registry-ui. Please remember the difference between the standard interface (
latest tag) and static interface (
Run the standard interface
You can run the standard interface see the website on your 80 port. You will be able to use the interface for many registry servers, but all the configuration via environment variables from the static interface will be unavailable.
docker run -d -p 80:80 joxit/docker-registry-ui:latest
Run the static interface
Some env options are available for use this interface for only one server.
URL: set the static URL to use (You will need CORS configuration). Example:
REGISTRY_URL: your docker registry URL to contact (CORS configuration is not needed). Example:
http://my-docker-container:5000. (Can't be used with
URL, since 0.3.2).
DELETE_IMAGES: if this variable is empty or
false, delete feature is deactivated. It is activated otherwise.
REGISTRY_TITLE: Set a custom title for your user interface when using
PULL_URL: Set a custom url for the docker pull command, this is useful when you use
REGISTRY_URLand your registry is on a different host (since 1.1.0).
NGINX_PROXY_HEADER_*: Set custom headers for your docker registry, usefull when you want to add your credentials. (Can be use only with
SHOW_CONTENT_DIGEST: Show content digest in docker tag list. Default:
CATALOG_ELEMENTS_LIMIT: Limit the number of elements in the catalog page. Default:
docker run -d -p 80:80 -e URL=http://127.0.0.1:5000 -e DELETE_IMAGES=true joxit/docker-registry-ui:static
REGISTRY_URL, this will add a proxy to your registry.
Your registry will be accessible here :
http://127.0.0.1/v2, this will avoid CORS errors (see #25).
registry:2 will communicate, both containers should be in the same network or use your private IP.
docker network create registry-ui-net docker run -d --net registry-ui-net --name registry-srv registry:2 docker run -d --net registry-ui-net -p 80:80 -e REGISTRY_URL=http://registry-srv:5000 -e DELETE_IMAGES=true -e REGISTRY_TITLE="My registry" joxit/docker-registry-ui:static
There are some examples with docker-compose and docker-registry-ui as proxy here or docker-registry-ui as standalone here.
Your server should be configured to accept CORS.
If your docker registry does not need credentials, you will need to send this HEADER:
If your docker registry need credentials, you will need to send these HEADERS:
http: headers: Access-Control-Allow-Origin: ['<your docker-registry-ui url>'] Access-Control-Allow-Credentials: [true] Access-Control-Allow-Headers: ['Authorization', 'Accept'] Access-Control-Allow-Methods: ['HEAD', 'GET', 'OPTIONS'] # Optional
An alternative for CORS issues is a plugin on your browser, more info here (thank you xmontero).
For deleting images, you need to activate the delete feature in your registry:
storage: delete: enabled: true
And you need to add these HEADERS:
http: headers: Access-Control-Allow-Methods: ['HEAD', 'GET', 'OPTIONS', 'DELETE'] Access-Control-Expose-Headers: ['Docker-Content-Digest']
If you are running the static interface don't forget the environment variable
Example of docker registry configuration file:
version: 0.1 log: fields: service: registry storage: delete: enabled: true cache: blobdescriptor: inmemory filesystem: rootdirectory: /var/lib/registry http: addr: :5000 headers: X-Content-Type-Options: [nosniff] Access-Control-Allow-Origin: ['http://127.0.0.1:8001'] Access-Control-Allow-Methods: ['HEAD', 'GET', 'OPTIONS', 'DELETE'] Access-Control-Allow-Headers: ['Authorization', 'Accept'] Access-Control-Max-Age:  Access-Control-Allow-Credentials: [true] Access-Control-Expose-Headers: ['Docker-Content-Digest'] auth: htpasswd: realm: basic-realm path: /etc/docker/registry/htpasswd
If you do not want to install the docker-registry-ui on your server, you may check out the Electron standalone application.
- Use docker-registry-ui as a proxy (use REGISTRY_URL)
- Use docker-registry-ui as standalone (use URL)
- Use docker-registry-ui with traefik
- Use docker-registry-ui with docker registry and Amazon s3 (#75)
- FIX revproxy to registry does not work when published under non-root url (#73)
- Use docker-registry-ui with HTTPS (#20)
- Unable to push image when docker-registry-ui is used as a proxy on non 80 port (#88)
- Add custom headers bases on environment variable and/or file when the ui is used as proxy (#89)
- UI showing same sha256 content digest for all tags + Delete is not working (#116)
- Electron-based Standalone Application (#129)
- Use docker-registry-ui as proxy with read-only right (#47)