Where should a developer read the tenancy namespace string that appears in OCIR image paths?
Select an answer to reveal the explanation.
Short Explanation
The path namespace is the Object Storage namespace on Tenancy Information—not a nickname you invent. Sometimes it matches a lowercased tenancy name, but you still read the field.
Full Explanation
The tenancy namespace string embedded in OCIR image paths is the tenancy’s Object Storage namespace, shown on the Tenancy Information page in the Console. It is an auto-generated identifier (sometimes resembling the tenancy name, sometimes not) and must be copied exactly into <registry-domain>/<tenancy-namespace>/<repository>:<tag>. Guessing wrong here is a frequent cause of login and push failures for new developers joining a municipal tenancy, because every image path and many username forms depend on that string.
Inventing a lowercase nickname that feels close to the tenancy display name produces a path OCIR does not recognize as your tenancy. The availability domain list under Networking identifies fault domains for compute networking, not registry path namespaces. The OCID of the first VCN in the root compartment is a network resource id and has no role as the OCIR path namespace segment.
Exam caveat: display name and Object Storage namespace are different fields—never assume they are identical without checking Tenancy Information, even when they look similar at a glance. Operational check: open Tenancy Details, copy the Object Storage namespace, compare it character-for-character to the namespace segment in your docker tag and docker login username strings, and only then attempt docker login and push to confirm the path resolves to your repositories.