Skip to content

Supported Images and Registries

Govern standard OCI image references and plan reviewable image-family migrations.

BIMP policy works with standard OCI image references found in supported repository artifacts.

You can use BIMP to govern standard OCI image references from a wide range of image providers and catalogues.

Image provider or catalogue Current BIMP behavior
Docker Official Images Standard OCI image references
Docker Hardened Images Standard OCI image references
Canonical Ubuntu and Chiselled Ubuntu Standard OCI image references
Microsoft official container images Standard OCI image references
Google Distroless Standard OCI image references
Red Hat Standard OCI image references
SUSE Standard OCI image references
Bitnami Standard OCI image references
Chainguard Standard OCI image references
Minimus Standard OCI image references

BIMP recognizes standard OCI image references from any OCI-compatible registry.

OCI-compatible registry examples include:

  • Amazon Elastic Container Registry (ECR);
  • Azure Container Registry (ACR);
  • Cloudsmith;
  • GitHub Container Registry (GHCR);
  • GitLab Container Registry;
  • Google Artifact Registry;
  • Harbor;
  • JFrog Artifactory;
  • Red Hat Quay; and
  • Sonatype Nexus Repository.

Private-registry access for builds remains the responsibility of the repository and its CI or deployment environment. A mapping does not grant registry credentials.

Image recommendations is an experimental feature that suggests images based on the current image tag. A recommendation is not an opinionated policy decision. Validate it against your organization’s policy and application requirements before using it in a mapping.

Image provider or catalogue Current recommendation behavior
Docker Official Images Suggests the latest stable matching image tag.
Minimus Suggests the latest stable matching reg.mini.dev image tag.

Recommendations retain the numeric precision and variant of the current tag, then resolve the suggested image’s current digest.

BIMP can seamlessly handle migrations between image providers and registries automatically when the change is limited to the image reference. Advanced migrations are on our roadmap. See Migrations for more information about using BIMP to automate migrations.