Bitnami: end of free versioned container images on Docker Hub

2025-08-28 · Publisher : Broadcom (Bitnami) · Domain : Cloud & DevOps

On 28 August 2025, Bitnami (Broadcom) switches its public catalogue: versioned images move to a "legacy" repository without updates, and production use is steered to the paid Bitnami Secure Images offering.

### Background Announced on 16 July 2025, the change to the public Bitnami catalogue takes effect on 28 August 2025. Versioned container images previously available free on Docker Hub (docker.io/bitnami) are moved to docker.io/bitnamilegacy, an archived repository with no updates or support. Only a limited selection of hardened images, with the "latest" tag, stays free for development. ### Key facts - Repository docker.io/bitnamisecure: a free subset of hardened images, "latest" tag only, intended for development. - Paid Bitnami Secure Images offering: production-ready images, continuous security updates, SBOMs and long-term-support branches. - Brownouts (test outages) of ten images for 24 hours on 28-29 August, 2-3 September and 17-19 September 2025. - Deletion of the public docker.io/bitnami catalogue postponed to 29 September 2025. - Source code and Helm charts stay published under the Apache 2.0 licence on GitHub. ### Why it matters Many Helm manifests, Dockerfiles and pipelines reference Bitnami images by version: an image pinned to a version that moves to the "legacy" repository no longer receives security fixes, and the test outages make the problem visible. For DevOps teams, it is a textbook case of uncontrolled dependency on a public registry: references must be inventoried, images mirrored in an internal registry, and a choice made between the paid offering, hardened images from another vendor or an in-house build. ### Takeaway A free dependency turned paid and broke pipelines: map your base images and keep an internal copy.

Tags : Conteneurs, Licence, Open Source, DevOps