Major Changes Coming to Bitnami's Container Image Catalog

Major Changes Coming to Bitnami's Container Image Catalog

On August 28th, 2025, Bitnami will implement significant changes to its public container image catalog, affecting how developers and organizations access and use their popular Docker images and Helm charts.


What's Changing

The transformation centers around three key areas:

  • Community Catalog Restructuring: Bitnami is discontinuing the generation of new Debian-based images and moving toward a more focused set of hardened, security-enhanced images. The free community tier will be limited to development use only, with images available exclusively under the "latest" tag.

  • Introduction of Bitnami Secure Images: Production workloads will need to migrate to the new Bitnami Secure Images offering. This provides enterprise-grade features including hardened operating systems, continuous security patches, SLSA Level 3 compliance, and comprehensive vulnerability documentation.

  • Legacy Repository Migration: All existing container images, including versioned tags, will be moved from the main public catalog to a new "Bitnami Legacy" repository. This legacy catalog will receive no further updates and is intended only as a temporary migration tool.

Timeline and Impact

The changes will roll out in phases.

  • Until August 28th: Users will see deprecation notices and should begin planning their migration strategies.

  • On August 28th (Transition Date): The public catalog will switch to the limited community subset, with legacy assets archived separately.

  • Post-Transition: Community users will only have access to the latest versions of a reduced set of images. Production users requiring full version support will need to subscribe to Bitnami Secure Images.

What Users Need to Do
Organizations should immediately:

  • Review CI/CD pipelines and update any dependencies on deprecated images.

  • For production workloads requiring continued support, security updates, and access to specific versions, subscribing to Bitnami Secure Images becomes essential or switch to official images.

  • As a temporary measure, existing deployments can point to the Bitnami Legacy repository. However, this should only be used during migration planning, as these images will not receive security updates. 

  • Verify the availability of the image tag on the Bitanmi Legacy Repository.

Quick Fix for Existing Helm Charts
If your Helm charts are currently failing to pull images after the transition, you can implement a temporary fix by updating your repository references from bitnami to bitnamilegacy. On the Devtron UI navigate to the Configure page of the helm chart then switch the  instances of :

repository: bitnami/your-image

to:

repository: bitnamilegacy/your-image

You can also update these references during a Helm upgrade using the --set flag:

helm upgrade myrelease oci://registry-1.docker.io/bitnamicharts/postgresql \
  --version 16.7.0 \
  --set image.repository=bitnamilegacy/postgresql \
  --set global.security.allowInsecureImages=true

If you want to get the list of all the Bitnami charts, please raise a ticket on https://enterprise.devtron.ai/portal/en/newticket.

Remember: This is only a temporary workaround to maintain functionality while you plan your migration to either the community-tier hardened images or Bitnami Secure Images.


Update:

 The Bitnami team has postponed the deletion of the Bitnami public catalog docker.io/bitnami until September 29th to give users more time to adapt to the upcoming changes.