3.2.1.3 Organization Image Repositories

Organization image repositories are the collections of images a company or team maintains under its own namespace in a registry, typically representing the internal services, tools, and base images that organization builds and depends on.

Structuring Repositories by Team or Service

A common pattern is to structure an organization's repositories so that each one corresponds to a single deployable service, with the namespace identifying either the organization as a whole or a specific team within it.

docker push registry.example.com/acmecorp/payments-api:1.0
docker push registry.example.com/acmecorp/notifications-worker:1.0

Internal Base Images as Shared Repositories

Organizations often maintain their own base images — pre-configured with internal tooling, certificates, or standard configuration — published as their own repositories, which other internal teams then build on top of.

FROM registry.example.com/acmecorp/base-python:3.12
COPY . /app
CMD ["python", "/app/main.py"]

Using a shared internal base image like this standardizes common setup across many internal services, while still letting each service repository remain otherwise independent.

Access Control at the Repository Level

Organizations frequently control who can push to or pull from specific repositories, often restricting push access to the team that owns a particular service while allowing broader pull access for anyone who needs to deploy or inspect it.

docker login registry.example.com
docker push registry.example.com/acmecorp/payments-api:1.1

Auditing and Governance Across Repositories

Centralizing an organization's images under its own namespace makes it practical to apply consistent governance — vulnerability scanning, retention policies, mandatory base image usage — across every repository the organization owns, rather than managing each one in isolation.

docker scan registry.example.com/acmecorp/payments-api:1.1

Why Organizing Repositories This Way Matters

A deliberately structured set of organization repositories, with consistent naming, shared base images, and centralized governance, scales far better than an ad hoc collection of independently managed images, particularly as the number of services and teams involved grows.