Build optimized Docker and OCI container images for Java applications with Maven or Gradle, without a Docker daemon.
klausmeyer/docker-registry-browser
A Ruby on Rails web interface for browsing and deleting images in a Docker Registry that implements the HTTP API V2.
- Stars
- 701
- Forks
- 64
- Open issues
- 9
- Last commit
- 4 days ago
What is it?
Docker Registry Browser is a web front end for private Docker registries that expose the Docker Registry HTTP API V2. It lets you see which repositories and tags a registry holds without running docker pull or curl against the API by hand.
The application is written in Ruby on Rails and ships as a Docker image. It runs on port 8080 and needs a SECRET_KEY_BASE environment variable, which can be generated with openssl rand -hex 64. Further configuration options are described in the project's documentation.
The interface covers an overview of repositories, a list of tags per repository, tag details, and tag deletion, as shown in the project's screenshots.
Key features
- 01Lists repositories and their tags from a Docker Registry HTTP API V2 endpoint.
- 02Shows details for individual image tags.
- 03Supports deleting tags from the registry through the web UI.
- 04Runs as a Docker container on port 8080, configured via environment variables.
Use cases
- Browsing the contents of a self-hosted private Docker registry.
- Cleaning up old or unwanted image tags in a registry.
- Giving team members a read-oriented view of available images without CLI access.
Quick start
- 1
Run the project with Docker, setting SECRET_KEY_BASE
docker run --name registry-browser -e SECRET_KEY_BASE="..." -p 8080:8080 klausmeyer/docker-registry-browser - 2
Generate a SECRET_KEY_BASE value
openssl rand -hex 64
Things to know
- Configuration options are described only in an external documentation file, so setup needs extra reading.
Topics
FAQ
- What is docker-registry-browser?
- A Ruby on Rails web interface for browsing and deleting images in a Docker Registry that implements the HTTP API V2. Docker Registry Browser is a web front end for private Docker registries that expose the Docker Registry HTTP API V2. It lets you see which repositories and tags a registry holds without running docker pull or curl against the API by hand.
- Is docker-registry-browser free to use? What license does it have?
- docker-registry-browser is open source under the MIT license. Check the license terms before using it in commercial products.
- Is docker-registry-browser still maintained?
- Actively maintained. The last commit to docker-registry-browser was on Nov 4, 2026.
- What can I use docker-registry-browser for?
- Browsing the contents of a self-hosted private Docker registry. Cleaning up old or unwanted image tags in a registry. Giving team members a read-oriented view of available images without CLI access.
- How do I install docker-registry-browser?
- Run the project with Docker, setting SECRET_KEY_BASE: docker run --name registry-browser -e SECRET_KEY_BASE="..." -p 8080:8080 klausmeyer/docker-registry-browser Generate a SECRET_KEY_BASE value: openssl rand -hex 64
- Where can I get docker-registry-browser?
- The source code and installation instructions are on GitHub: https://github.com/klausmeyer/docker-registry-browser
Summary generated by AI from the project's README. GitHub stats refresh daily.
Related projects
A command-line tool to inspect, copy, sync, sign and delete container images across registries and local storage without a daemon.
Self-hosted GitLab Community Edition: a Ruby on Rails web app for managing Git repositories, code reviews, CI/CD and issue tracking.
A modern, self-hosted web UI for managing Docker containers, images, and Compose stacks.
A WebUI for automatically updating Docker containers and sending notifications about container changes.
A Python framework for building terminal and web user interfaces with a simple, component-based API.