> [!IMPORTANT]
> After evaluating the impact and community feedback, the Bitnam…i 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.
>
> To raise awareness before the registry deletion, we will run a series of **brownouts** over the coming weeks. During each brownout, a set of 10 container images from docker.io/bitnami will be temporarily unavailable for 24 hours. The scheduled brownouts are:
>* August 28, 08:00 UTC → August 29, 08:00 UTC
>* September 2, 08:00 UTC → September 3, 08:00 UTC
>* September 17, 08:00 UTC → September 19, 08:00 UTC
>
>The list of affected applications will be published on the day of each brownout via our usual channels.
>
>As previously announced, since August 28th, we have not published new Bitnami container images or Helm charts to Docker Hub in OCI format. The source code for containers and Helm charts remains available on GitHub under the Apache 2.0 license.
---------------
### 📢 Overview
As of August 28th, 2025, the Bitnami public catalog will undergo the following changes:
- **Community catalog**
- Disable images generation for Debian-based images and gradually move existing ones to a [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy).
- A focused set of more hardened, more secure images. These free images are intended for development and are only available on the “latest” tag. You can find them at https://hub.docker.com/u/bitnamisecure.
- Helm charts and container images' open-source code will continue to be maintained up-to-date and accessible on GitHub under the Apache 2 license.
- **Bitnami Secure Images**
- Production-ready, enterprise-grade containers and Helm charts will move under the Bitnami Secure Images offering.
- Benefits include:
- Hardened, low-attack-surface operating system
- Continuous rebuilds with the latest security patches (SLSA Level 3)
- Industry-standard CVE transparency (VEX, KEV)
- SBOMs and compliance artifacts
- Enterprise support and LTS branches
- Access to the entire catalog of applications (over 280)
- Minimal distroless runtime images
- **Legacy repository migration**
- All existing container images, including older or versioned tags (e.g., _2.50.0_, _10.6_), will be moved from the public catalog (`docker.io/bitnami`) to the [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy) (`docker.io/bitnamilegacy`). This legacy catalog will receive no further updates or support and should only be used for temporary migration purposes.
- Exception: Images based on distros deprecated from the Bitnami catalog more than 3 years ago (tags: `debian-8`, `debian-9`, `debian-10`, `centos-7`, `ol-7`) will not be copied.
- Suppose your deployed Helm chart is failing to pull images from `docker.io/bitnami`. In that case, you can resolve this by subscribing to Bitnami Secure Images, ensuring that the Helm charts receive continued support and security updates. As a temporary workaround, you can upgrade to the same version and update the repository parameter for each container image to the [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy).
### 🗓️ Timeline
- **Now – August 28th, 2025**
- You will see deprecation notices in READMEs and documentation.
- Plan your migration: Update CI/CD pipelines, Helm repos, and image references.
- Start trying out the new hardened images available to the community today at https://hub.docker.com/u/bitnamisecure.
- **August 28th, 2025**
- The [public catalog](https://hub.docker.com/u/bitnami) switches to the limited community-tier subset of container images (the same images that are initially available at https://hub.docker.com/u/bitnamisecure).
- Legacy assets are archived in the [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy).
- **Post-August 28th, 2025**
- For development purposes, community-tier users are restricted to pulling only the most recent ‘latest’ tags of the limited community-tier subset of container images.
- Production users should subscribe to Bitnami Secure Images for full version support at https://www.arrow.com/globalecs/uk/products/bitnami-secure-images/#CTA.
<div align="center">
<img width="639" height="830" alt="Image" src="https://github.com/user-attachments/assets/7955df63-96fc-4d77-8003-7ca04bd9ea4b" />
</div>
---------------
### FAQ
**Q: What is the [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy)?**
**A:** The [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy) is an archive that will host all older container images, including versioned tags (e.g., _2.50.0_, _10.6_) that are no longer maintained in the main Bitnami catalog. These images will not receive updates, fixes, or support and should only be used as a temporary fallback for migration purposes. Although there are no updates to the container images, the Bitnami project continues to make its source code available at [bitnami/containers](https://github.com/bitnami/containers) under the Apache 2 license.
**Q: How is [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy) different than [_Bitnami Mainline_ repository](https://hub.docker.com/u/bitnami)?**
**A:**
- The [_Bitnami Mainline_ repository](https://hub.docker.com/u/bitnami) (`docker.io/bitnami`) currently hosts regularly updated and supported container images, including free and enterprise-grade offerings.
- The [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy) will contain archived versions that will no longer receive updates. It is provided solely to help with migration during the transition.
After August 28th, 2025, only a limited set of hardened images will remain in the [_Bitnami Mainline_ repository](https://hub.docker.com/u/bitnami). All others will be moved to the [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy).
**Q: What do users of [_Bitnami Mainline_ repository](https://hub.docker.com/u/bitnami) need to do before August 28th, 2025?**
**A:** Users should:
1. Review and update CI/CD pipelines to avoid relying on deprecated images.
2. Consider subscribing to Bitnami Secure Images if they need continued support, security updates, or access to full version history at https://www.arrow.com/globalecs/uk/products/bitnami-secure-images/#CTA.
3. Upgrade their deployments
1. If the deployed application belongs to the limited set of hardened images available under the new free community tier, double-check that the used tags are still updated.
2. Otherwise, point to the [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy) as a temporary workaround.
**Q: Are Bitnami’s free images going away?**
**A:** Not entirely. Bitnami will continue to offer a limited subset of free, latest-version images intended for development use. These images will be more hardened and secure, but older versions and many applications will be removed from the free tier and moved to the [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy). You can browse the images available for free at https://hub.docker.com/u/bitnamisecure until August 28th, after which the main Bitnami registry will have the same content.
**Q: How can I obtain continued support for an application that is no longer available for free?**
**A:** To continue receiving updates, security patches, and enterprise support for older or specific versions of an application, you can subscribe to the Bitnami Secure Images offering. This includes access to:
- Long-term support (LTS) branches
- Distroless and hardened images
- SBOMs, CVE transparency (VEX/KEV), and compliance artifacts
- SLSA Level 3 build processes
The Bitnami project continues to make its source available at [bitnami/containers](https://github.com/bitnami/containers) under the Apache 2 license; images can be built from source.
**Q: What will happen to the existing OCI Helm charts?**
**A:** The already packaged Helm charts will remain available at `docker.io/bitnamicharts` as OCI artifacts, but they will no longer receive updates*. Deploying these charts will not work out-of-the-box* unless you override the bundled images with valid ones.
_*except for the BSI images included in the free community-tier subset._
**Q: What will happen to the Helm charts source code?**
**A:** No changes are being made to the helm chart source code on [https://github.com/bitnami/charts](https://github.com/bitnami/charts). It continues to be available under the Apache 2 license.
**Q: How can I get a complete list of what images and charts are available from Bitnami, both free and commercial?**
**A:** We are working on an enhanced public directory that inventories everything available from Bitnami. In the meantime, you can determine the subset of images that will remain free/community by looking at what is in this registry: [BSI Dockerhub](https://hub.docker.com/u/bitnamisecure/). All remaining Bitnami images/charts, as well as new ones being developed, are available via custom private registries provided as part of a BSI commercial subscription.
**Q: How can I get continued support for Helm charts?**
**A:** If your deployed Helm chart is failing to pull images from docker.io/bitnami, to ensure continued support and access to security updates, we recommend subscribing to Bitnami Secure Images at https://www.arrow.com/globalecs/uk/products/bitnami-secure-images/#CTA.
As a temporary workaround, you can keep using the same Helm chart version by pointing it to the “[_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy), which hosts archived images with no further updates. For that, you can upgrade to the same chart version and update the repository parameter of each container image to the [_Bitnami Legacy_ repository](https://hub.docker.com/u/bitnamilegacy):
- List container images: ``grep 'repository.*REPOSITORY_NAME/' postgresql/README.md | awk -F'\`' '{print $2, $(NF-1)}'``
- Upgrade modifying repositories: `helm upgrade RELEASE_NAME oci://registry-1.docker.io/bitnamicharts/CHART_NAME --version SAME_VERSION --set REPOSITORY_REFERENCE=bitnamilegacy`
- `REPOSITORY_REFERENCE` is the path to the repository parameter as it is in the values.yaml for each container image.
- Example:
```console
$ grep 'repository.*REPOSITORY_NAME/' postgresql/README.md | awk -F'\`' '{print $2, $(NF-1)}'
image.repository REPOSITORY_NAME/postgresql
volumePermissions.image.repository REPOSITORY_NAME/os-shell
metrics.image.repository REPOSITORY_NAME/postgres-exporter
```
```
$ helm upgrade mypostgres oci://registry-1.docker.io/bitnamicharts/postgresql \
--version 16.7.0 \
--set image.repository=bitnamilegacy/postgresql \
--set volumePermissions.image.repository=bitnamilegacy/os-shell \
--set metrics.image.repository=bitnamilegacy/postgres-exporter \
--set global.security.allowInsecureImages=true
```
--------------------
> [!NOTE]
> [Sealed Secrets](https://github.com/bitnami-labs/sealed-secrets), [charts-syncer](https://github.com/bitnami/charts-syncer) and [minideb](https://github.com/bitnami/minideb) remain unaffected by these changes. Container images for those projects will continue to be released on [docker.io/bitnami](`http://docker.io/bitnami`) as usual without any modifications.