A web UI, authentication service, and event recorder for private Docker Registry v2.
docker-registry-web is a web-based user interface and management tool for private Docker Registry v2 deployments. It provides a visual way to browse container images, adds token-based authentication with role-based permissions, and records registry events for auditing. It solves the problem of managing and securing private Docker registries without relying on proprietary solutions.
DevOps engineers, platform teams, and organizations running private Docker registries who need a visual management interface, enhanced security, and audit capabilities.
Developers choose docker-registry-web because it is a lightweight, open-source alternative to commercial registry management tools, offering essential features like authentication, RBAC, and audit logging while being easy to self-host and integrate with existing Docker Registry setups.
Web UI for private docker registry v2
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a comprehensive web interface to browse Docker repositories, tags, and images, as highlighted in the features list, making it easy to navigate and manage container images visually.
Offers token-based authentication with configurable role-based permissions, allowing fine-grained access control via ACLs and glob matching, as described in the role system section.
Records Docker registry notifications for audit and compliance, enabling tracking of push, pull, and delete events without modifying the core registry.
Designed for seamless integration with Docker, with clear run commands, Docker Compose examples, and environment variable support for straightforward setup and customization.
Enabling token authentication requires generating SSL certificates, coordinating multiple configuration files, and aligning settings between registry and web app, which can be error-prone and time-consuming, as shown in the detailed steps.
The README warns that configuration files are not backward compatible with versions prior to 0.1.0, necessitating migration efforts and potential downtime during upgrades.
Lacks built-in features like image vulnerability scanning, automated cleanup, or native CI/CD integrations, which are common in more comprehensive registry management tools like Harbor.