Registry Management #
Registry Management saves you from the hassle of managing different images in different places. BuildPiper Registry Management scans for CVE vulnerabilities every time you onboard any application — just use the image link, and you are good to build any application.
Overview & Key Terminologies #
Registry Management centralises your container image lifecycle — eliminating version conflicts, enforcing security scanning, and providing a single source of truth across all teams and environments.
Why Use Registry Management? #
Prevents unauthorized access and blocks deployment of images with known vulnerabilities. CVE scan runs automatically on every onboarding.
Provides a “single source of truth” for all team members — ensuring the same image is used across different environments as per requirements.
Enables faster image pulls by caching and centralising registry access, reducing build pipeline latency.
Who Can Onboard Images in Registry? #
📌
RBAC-Controlled Access
Registry onboarding is governed by BuildPiper’s Role-Based Access Control (RBAC). Only users with Super Admin or Manager / DevOps roles have the permission to add and configure container registries within BuildPiper.
Step-by-Step Configuration Guide #
1

2

3

4
BuildPiper integrates with nearly all registry platforms available on the market. Select the registry platform that matches your organisation’s requirements.
▸
Microsoft’s cloud-based registry for private Docker container images.
▸
Sonatype repository manager supporting Docker for enterprise artifact management.
▸
Secure, managed container registry by Alibaba Cloud for Docker images.
▸
Host and manage Docker images directly within GitHub workflows.
▸
Fully managed AWS service to store, manage, and deploy Docker images.
▸
Secure, private Docker image storage by Google Cloud Platform.
▸
Universal repository manager for advanced Docker image management.
▸
World’s largest public container image library and default Docker registry.
▸
Managed container registry by Huawei Cloud for reliable image distribution.
▸
Connect any third-party or self-hosted registry via Docker Registry HTTP API.
5
① Enter Registry Name #
nginx-latest— an Nginx registry with the latest version tag② Enter Registry URL #
https://registry-1.docker.io③ Enter Registry Credentials #

④ Save and Verify Connection #

CONNECTED— Registry is live and working
NOT CONNECTED— Check credentials or URL
📘 BuildPiper Documentation · Registry Management
Last updated: March 2026