Skip to main content

Private container registries

See also

Modern development workflows often rely on private container registries to securely host container images that are not intended to be publicly available.

Divio supports private registry integration, enabling applications to pull container images from private registries during the build process.

Why use a private container registry?​

There are several reasons to use private registries:

  • Security: Control access to sensitive or proprietary images.
  • Custom base images: Store internal base images to ensure consistency across environments.
  • CI/CD workflows: Integrate with pipelines that automatically build and push images.

With private registry credentials support, Divio can now pull private images securely during the build process.

Supported registries​

Divio supports credentials for most container registry providers, including:

  • Docker Hub (docker.io)
  • GitLab Container Registry (registry.gitlab.com)
  • GitHub Container Registry (ghcr.io)
  • Other OCI-compatible registries

Example​

If you use GitLab CI/CD to build container images, you can push to a private GitLab registry and reference those images in a Dockerfile:

FROM registry.gitlab.com/my-own/private-repository:2.1.3