Docker Registry User Interface

• 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 ?

• Can I run the container with an unprivileged user ?

• Can I use the UI with a docker hub mirror and show library/* images ?

• How to fix CORS issue on s3 bucket ?

• Why my docker registry server is returning an error pagination number invalid ?

• I'm using NGINXPROXYPASS_URL, my registry server has been recreated and the UI cannot connect with the message [error] 176#176: *2 connect() failed (111: Connection refused) while connecting to upstream, what can I do?

Need more informations ? Try my examples or open an issue.

Available options

You can run the container with the unprivileged user nginx, see the discussion #224.

Some env options are available for use this interface for only one server (when SINGLE_REGISTRY=true).

• REGISTRY_URL: The default url of your docker registry. You may need CORS configuration on your registry. This is usually the domain name or IP of your registry reachable by your computer (e.g http://registry.example.com). (default: derived from the hostname of your UI).
• REGISTRYTITLE: Set a custom title for your user interface. (default: value derived from REGISTRYURL) (see #28 and #32). Since 0.3.4
• PULLURL: Set a custom url when you copy the docker pull command (see #71). (default: value derived from REGISTRY_URL). Since 1.1.0
• DELETE_IMAGES: Set if we can delete images from the UI. (default: false)
• SHOWCONTENTDIGEST: Show/Hide content digest in docker tag list (see #126 and #131). (default: false). Since 1.4.9
• CATALOGELEMENTSLIMIT: Limit the number of elements in the catalog page (see #39, #127, #132) and #306. (default: 1000). Since 1.4.9
• SINGLE_REGISTRY: Remove the menu that show the dialogs to add, remove and change the endpoint of your docker registry. (default: false). Since 2.0.0
• NGINXPROXYPASSURL: Update the default Nginx configuration and set the proxypass to your backend docker registry (this avoid CORS configuration). This is usually the name of your registry container in the form http://registry:5000. Since 2.0.0
• NGINXPROXYHEADER*: Update the default Nginx configuration and set custom headers for your backend docker registry via environment variable and file (/etc/nginx/.env). Only when NGINXPROXYPASSURL is used (see #89). Since 1.2.3
• NGINXPROXYPASSHEADER*: Update the default Nginx configuration and forward custom headers to your backend docker registry via environment variable and file (/etc/nginx/.env). Only when NGINXPROXYPASSURL is used (see #206). Since 2.1.0
• NGINXLISTENPORT: Listen on a port other than 80, you can also change the default user and set to nginx --user nginx (see #224 and #234). (default: 80 when the user is root, 8080 otherwise). Since 2.2.0
• NGINXRESOLVER: Add resolver directive to the nginx configuration for dynamic dns resolving. The value when you are using a docker network is 127.0.0.11, you can set a custom DNS server too with a valid time. This is not needed when you are using kubernetes. (see #333 and #339). (default: `). Since 2.5.5
• DEFAULTREGISTRIES: List of comma separated registry URLs (e.g http://registry.example.com,http://registry:5000), available only when SINGLEREGISTRY=false (see #219). (default: ). Since 2.1.0
• READONLYREGISTRIES: Deactivate dialog for remove and add new registries, available only when SINGLEREGISTRY=false (see #219). (default: false). Since 2.1.0
• SHOWCATALOGNBTAGS: Show number of tags per images on catalog page and hide images with 0 tags. This will produce + nb images requests, not recommended on large registries (see #161 and #239). (default: false). Since 2.2.0
• HISTORYCUSTOMLABELS: Expose custom labels in history page, custom labels will be processed like maintainer label (see #160 and #240). Since 2.2.0
• USECONTROLCACHEHEADER: Use Control-Cache header and set to no-store, no-cache. This will avoid some issues on multi-arch images (see #260 and #265). This option requires registry configuration: Access-Control-Allow-Headers with Cache-Control. (default: false). Since 2.3.0
• THEME: Chose your default theme, could be dark, light or auto (see #283). When auto is selected, you will have a switch to manually change from light to dark and vice-versa (see #291). (default: auto). Since 2.4.0
• THEME*: See table in Theme options section (see #283). Since 2.4.0
• TAGLISTORDER: Set the default order for the taglist page, could be num-asc;alpha-asc, num-desc;alpha-asc, num-asc;alpha-desc, num-desc;alpha-desc, alpha-asc;num-asc, alpha-asc;num-desc, alpha-desc;num-asc or alpha-desc;num-desc (see #307). (default: alpha-asc;num-desc). Since 2.5.0
• CATALOGDEFAULTEXPANDED: Expand by default all repositories in catalog (see #302). (default: false). Since 2.5.0
• CATALOGMINBRANCHES: Set the minimum repository/namespace to expand (e.g. joxit/docker-registry-ui joxit/ is the repository/namespace). Branching can be disabled if min and max are set to 0. (see #319). (default: 1). Since 2.5.0
• CATALOGMAXBRANCHES: Set the maximum repository/namespace to expand (e.g. joxit/docker-registry-ui joxit/ is the repository/namespace). Branching can be disabled if min and max are set to 0. (see #319). (default: 1). Since 2.5.0
• TAGLISTPAGESIZE: Set the number of tags to display in one page. (default: 100). Since 2.5.0
• REGISTRY_SECURED: By default, the UI will check on every requests if your registry is secured or not (you will see 401 responses in your console). Set to true if your registry uses Basic Authentication and divide by two the number of call to your registry. (default false). Since 2.5.0
• SHOWTAGHISTORY: Whether to show the tag history feature or not. Allows to simplify the user interface by hiding it form the tag list if set to false. (default: true).

storage:
    delete:
      enabled: true

http:
  headers:
    Access-Control-Allow-Methods: ['HEAD', 'GET', 'OPTIONS', 'DELETE']
    Access-Control-Allow-Headers: ['Authorization', 'Accept', 'Cache-Control']
    Access-Control-Expose-Headers: ['Docker-Content-Digest']

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:8000']
    Access-Control-Allow-Methods: ['HEAD', 'GET', 'OPTIONS', 'DELETE']
    Access-Control-Allow-Headers: ['Authorization', 'Accept', 'Cache-Control']
    Access-Control-Max-Age: [1728000]
    Access-Control-Allow-Credentials: [true]
    Access-Control-Expose-Headers: ['Docker-Content-Digest']
auth:
  htpasswd:
    realm: basic-realm
    path: /etc/docker/registry/htpasswd

• Use docker-registry-ui as a proxy (use REGISTRYURL)
• 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)
• Use DEFAULTREGISTRIES and READONLYREGISTRIES (#219)