A public-works CI job must push a tagged image to OCIR. Which pieces belong in the fully qualified image path?
Select an answer to reveal the explanation.
Short Explanation
An OCIR path is domain, namespace, repository, and version. Miss the namespace, use the wrong region domain, or swap in the tenancy display name and the push fails.
Full Explanation
A fully qualified OCIR image path for the public-works CI push must include the regional registry domain, the tenancy Object Storage namespace, the repository name, and a version tag: <registry-domain>/<tenancy-namespace>/<repository>:<version>. That string is what docker tag and docker push target, and what later pulls must repeat. Missing any segment usually produces auth failures, “repository not found,” or pushes to an unintended name.
Shipping only the repository short name and a random UUID with no registry domain leaves Docker without a remote destination host and without the tenancy namespace OCIR requires. Encoding tenancy display name, availability domain, and Block Volume OCID invents a path that is not an OCIR repository reference. Using a compartment OCID alone as the image name with no tag confuses IAM resource identifiers with distribution image references; compartments authorize access, they are not image names.
Exam caveat: the registry domain must match the region that holds the repository; a correct-looking path with the wrong regional host still fails. Operational check: before CI push, echo the composed image name, verify domain region, namespace, repo, and tag against the Console, then push and confirm the tagged image appears under that repository in the expected region.