Study guide
4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management
OCI 2026 Architect Professional 1Z0-997-26
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Exam Overview & Architecture Foundations
1.1 Exam Logistics, the 2026 Blueprint & How to Use This Guide 1.2 The OCI Well-Architected Framework & Architectural Tradeoffs
2 Chapter 2: High Availability & Resilient Design
2.1 Availability Domains, Fault Domains, Instance Pools & Load Balancers 2.2 OCI DNS Traffic Steering, Geolocation & Health Checks 2.3 Block Volume Replication, Volume Groups & Backup Policies 2.4 Object Storage Replication, Versioning & Retention Rules (WORM)
3 Chapter 3: Full Stack Disaster Recovery
3.1 Full Stack Disaster Recovery: Protection Groups, Members & Permissions 3.2 DR Plans: Switchover, Failover, Prechecks & Plan Execution 3.3 DR Drills, Plan Customization & Operational Readiness
4 Chapter 4: Container Instances, OCIR & OCI DevOps
4.1 Containerization, Microservices & OCI Container Instances 4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management 4.3 OCI DevOps: Code Repositories, Build Pipelines & Deployment Strategies
5 Chapter 5: OCI Kubernetes Engine (OKE)
5.1 OKE Cluster Types, Node Options & Cluster Creation 5.2 OKE Networking: VCN-Native Pod Networking vs. Flannel, Subnet Sizing & Load Balancers 5.3 OKE Workload Identity, Secrets & Persistent Storage
6 Chapter 6: Serverless Functions & API Gateway
6.1 OCI Functions: Concepts, Invocation Modes, Integrations & Image Security 6.2 API Gateway: Authentication, JWT Validation, Rate Limiting & Usage Plans
7 Chapter 7: Messaging & Event-Driven Design
7.1 OCI Streaming, OCI Queue & Messaging Patterns for Microservices 7.2 OCI Events, Event Rules & OCI Notifications Fan-Out
8 Chapter 8: Infrastructure as Code with Terraform & Resource Manager
8.1 Infrastructure as Code with Terraform and the OCI Provider 8.2 OCI Resource Manager: Stacks, Jobs, Drift Detection & Private Endpoints
9 Chapter 9: Identity & Multi-Tenancy Governance
9.1 IAM Policy Design: Verbs, Conditions, Dynamic Groups & Principals 9.2 Organizations Management, Governance Rules & Compartment Quotas
10 Chapter 10: Security Posture with Cloud Guard & Security Zones
10.1 Cloud Guard: Detector Recipes, Problems, Scores & Responders 10.2 Security Zones & Vulnerability Scanning
11 Chapter 11: Secure Access & Network Protection
11.1 Layered Network Security: Security Lists, NSGs & Private Access to Services 11.2 OCI Bastion: Managed SSH, Port Forwarding & SOCKS5 Sessions 11.3 Zero Trust Packet Routing (ZPR): Security Attributes & Intent-Based Policy 11.4 OCI Network Firewall: Policies, Inspection Routing, Tunnel Inspection & Private NAT
12 Chapter 12: Application & Data Protection: WAF, Certificates & Vault
12.1 OCI Web Application Firewall: Policies, Modules, Actions & Enforcement Points 12.2 OCI Certificates: Private CAs, TLS Certificates, Renewal & Integrations 12.3 OCI Vault Key Management: Vault Types, Protection Modes, Dedicated KMS & External KMS 12.4 Vault Secrets: Versions, Rotation States, Automatic Generation & Rotation
13 Chapter 13: Base Database Service & Autonomous AI Database
13.1 Base Database Service: DB Systems, RAC, Data Guard, Cloning & Maintenance 13.2 Autonomous AI Database: Workload Types, Deployment Options, Services & Connectivity 13.3 Operating Autonomous AI Database: Scaling, Cloning, Backups, Patching & Self-Tuning 13.4 Autonomous Data Guard & Backup-Based Disaster Recovery for Autonomous AI Database
14 Chapter 14: Recovery Service, Global Distribution & OCI Cache
14.1 Autonomous Recovery Service: Protection Policies, Real-Time Protection & Retention Lock 14.2 Globally Distributed Autonomous AI Database: Sharding, Data Placement & Replication 14.3 OCI Cache: Valkey and Redis Clusters, Sharding, Security & Cross-Region Replication
15 Chapter 15: Monitoring, Alarms & Notifications
15.1 OCI Monitoring: Metrics, Namespaces, Custom Metrics & Monitoring Query Language 15.2 Alarms & Notifications: Trigger Rules, Absence Alarms, Split Messages, Suppression & Delivery
16 Chapter 16: Logging, Audit, Connector Hub & Search
16.1 OCI Logging: Log Groups, Service Logs, Custom Logs & the Unified Monitoring Agent 16.2 Logging Search, the Logging Query Language & OCI Audit 16.3 Connector Hub: Moving Logs, Metrics, Queue Messages & Streams Between Services 16.4 OCI Search with OpenSearch & Resource Search for Observability
4.2 OCI Container Registry: Repositories, Push & Pull, and Image Management
Key Takeaways Explain This Topic AI
OCIR is an Open Container Initiative (OCI)-compliant registry that supports the Docker V2 API, multi-architecture manifest lists, and Helm charts.
Docker clients log in with the tenancy's Object Storage namespace plus username (namespace/username) and use an auth token as the password.
Each region allows up to 500 repositories using up to 500 GB in total, and each repository can hold up to 100,000 images.
Retention policies delete images that have not been pulled, or not been tagged, for a set number of days, and each region has its own global retention policy.
Image signatures are created with an RSA asymmetric key in OCI Vault; AES symmetric keys cannot be used to sign images.
Last updated: October 2026
What OCIR Provides
OCI Container Registry (also called Oracle Cloud Infrastructure Registry, or OCIR) is an Oracle-managed registry for storing, sharing, and managing container images. It is Open Container Initiative compliant , implements the Docker Registry HTTP API V2 , and supports:
Standard docker and podman push and pull commands.
Manifest lists (multi-architecture images), so one tag can serve both AMD64 and ARM (Ampere) nodes.
Helm charts , stored as OCI artifacts.
Private repositories (authenticated) and public repositories (anyone with the URL can pull).
OCIR is regional . Each region has its own registry endpoint, and a repository lives in one region.
Endpoints and Image Paths
You address a region's registry with its region key, for example iad.ocir.io for Ashburn or phx.ocir.io for Phoenix. A full image path has three parts after the endpoint: <region-key>.ocir.io/<tenancy-namespace>/<repository-name>:<tag>
iad.ocir.io/ansh81vru1zp/orders/api:2.4.1
The tenancy namespace is the auto-generated Object Storage namespace string shown on the Tenancy Information page. It is not the tenancy name. Repository names can include a path, such as orders/api , to organize images by project.
Authentication: Auth Tokens
To log in from Docker, a user runs docker login iad.ocir.io and enters:
Username : <tenancy-namespace>/<username> , for example ansh81vru1zp/jdoe@acme.com . Older tenancies federated with Oracle Identity Cloud Service use <tenancy-namespace>/oracleidentitycloudservice/<username> .
Password : an auth token generated for the user, not the console password.
Automated systems should avoid long-lived personal tokens where possible. OCI DevOps build pipelines, for example, push to OCIR using the pipeline's resource principal and IAM policies, and Container Instances can store registry credentials in a Vault secret.
IAM Policies for Repositories
Repository access is controlled with the repos resource type: Allow group Developers to manage repos in compartment AppDev
- Allow group Deployers to read repos in compartment AppDev
- Allow dynamic-group BuildPipelines to manage repos in compartment AppDev
Pulling needs read access to the repository; pushing needs manage access. Public repositories can be pulled without authentication, so only mark a repository public when the images contain nothing sensitive.
Limits and Private Access
- Limit Value
- Repositories per region Up to 500
- Total storage per region Up to 500 GB (contact Oracle for more)
- Images per repository Up to 100,000
Resources in a private subnet, such as OKE worker nodes, can pull from OCIR privately through a service gateway in the same region. No internet gateway is needed, and traffic stays on Oracle's network.
Image Management Task 1: Retention Policies
Old development builds accumulate quickly. Image retention policies delete images automatically when they match selection criteria:
Images that have not been pulled for a certain number of days.
Images that have not been tagged for a certain number of days.
Images whose tags are listed as exempt are never deleted.
Each region has one global image retention policy that applies to all repositories. Its default criteria retain all images, so nothing is deleted until you change it. Custom retention policies override the global policy for the repositories you add to them, and only one custom policy can apply to a repository at a time. An hourly process deletes matching images, but a newly created or updated policy is ignored for several hours as a cooling-off period so you can refine its criteria. Because policies are regional, you must create matching policies in every region that holds copies of your images.
Image Management Task 2: Signing and Verification
Supply-chain security requires proof that an image came from your pipeline and was not altered. OCIR supports image signing with a master encryption key from OCI Vault :
Push the image to OCIR.
Sign it with an RSA asymmetric Vault key and key version. AES symmetric keys cannot sign images. oci artifacts container image-signature sign-upload --compartment-id <compartment-ocid> --kms-key-id <key-ocid> --kms-key-version-id <key-version-ocid> --signing-algorithm SHA_224_RSA_PKCS_PSS --image-id <image-ocid>
A signature is tied to the image's OCID, so it applies to that specific push. An image can carry several signatures from different keys. Runtimes can then refuse unsigned images : OKE clusters and OCI Functions applications can be configured with image verification policies that only run images signed by specified Vault keys.
Image Management Task 3: Vulnerability Scanning
You enable scanning by adding an image scanner to a repository. OCIR then uses the Vulnerability Scanning service to:
Scan every image pushed to the repository.
Immediately scan the four most recently pushed images if the repository already had images.
Re-scan automatically when new vulnerabilities are added to the CVE database.
Scan results list the CVEs found in each image. A deployment pipeline can check those results and stop a release that contains critical vulnerabilities.
Making Images Available in Several Regions
Because OCIR is regional, a multi-region or DR design must ensure the standby region can pull the same image versions. A common pattern is for the build pipeline to push each released image to the registry in every target region, and to deploy by image digest rather than a mutable tag so both regions run byte-identical images. Retention policies, signing keys, and scanners must also be configured in each region.