Create a Private Container Registry
Create a Private Container Registry via the DCD. After creating a Private Container Registry, you can store and manage Docker and OCI images privately, enable vulnerability scanning to detect CVEs in your artifacts, and choose the deployment location where your Private Container Registry and its artifacts will be hosted.
Prerequisites: Ensure you have the appropriate permissions. Only contract administrators, owners, and users with the Access and manage Private Container Registry permission can create a Private Container Registry.
1. In the DCD, go to Menu > Containers > Container Registry.
2. Select Add a Registry in the Container Registry window to create a new Private Container Registry.
3. Provide an appropriate Name.
Important:
You cannot change the Name or the Location after the creation of a Private Container Registry.
Ensure that the Private Container Registry Name is:
Globally unique across all customers.
Contains only alphanumeric characters and dashes.
Is between 3 and 63 characters long.
Begins with a character between a-z.
Ends with an alphanumeric character.
4. Choose the Location from the drop-down list where you want your Private Container Registry to run and your artifacts to be stored.
5. Turn on the Vulnerability Scanning toggle.
Important: It is recommended that you create your Private Container Registry with Vulnerability Scanning enabled:
It is a paid add-on and you will be charged for this service.
You can turn it on for a Private Container Registry which does not have it enabled.
You cannot disable it once it is enabled.
Your container image artifacts will be scanned for CVEs when pushed to a Private Container Registry and every time CVE databases are updated with newly identified CVEs.
6. Click Add Registry.
Result: Your Private Container Registry is ready to use when its status is updated to Running.
Last updated
Was this helpful?