> \

> \ > > \--------------- > > \### 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://go-vmware.broadcom.com/contact-us. > 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://go-vmware.broadcom.com/contact-us. > 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. In short, there will probably be substantial work in the future to deal with these problems. If an alternate provider cannot be found I may have to take on supporting the Docker container and Helm chart myself. It may also be worth considering an alternative service, but I am not aware of a viable one. Given that all of my video content is on this service, this presents a substantial problem for my platform and workflow. The future of MinIO on eom.dev is uncertain, and I am open to suggestions for how best to deal with these issues.