Problem:
As of September 29th, 2025 (originally August 28th) Bitnami will be migrating their Docker images to the Bitnami Legacy repository.
All existing container images, including older or versioned tags will be removed from the public catalog (docker.io/bitnami)
CircleCI Server uses these images for data layer services including Redis, PostgreSQL, MongoDB, and RabbitMQ.
Action is required to ensure your CircleCI Server environment is prepared before Bitnami sunsets access to these resources at their existing paths.
If any of the kubernetes nodes restart after September 29, 2025, without updating image references to Bitnami Legacy repository, pods will fail to pull images from the original repository and services will enter an ImagePullBackOff state. This means critical data services including Redis, PostgreSQL, and MongoDB will not start, resulting in complete service disruption for your CircleCI Server installation.
Solutions:
The first 2 solutions are preferred and recommended solutions. If you are unable to make either of these changes, then the last 2 would also be acceptable, but not ideal.
The Helm charts have now been updated in the latest releases of actively supported versions of CircleCI Server. Upgrading your environment to a version no longer dependent on the Bitnami repositories will ensure continuity of your K8S nodes' ability to pull the images as needed.
Solution 2 - Modify Your values.yaml File to point to Azure
You can modify your values.yaml files to point to the Azure repository for server images as an alternative and run
helm upgradewith the new configuration, found here:Update the
image.registrykey for the service tohttps://cciserver.azurecr.io/, for example:mongodb: image: registry: cciserver.azurecr.io
Solution 3 - Utilize Air Gapped Installation Instructions
Using the documented procedure in our "Air Gapped Installation" to ensure your site has reliable, local access to the affected images after the Bitnami retirement
Solution 4 - Manually patch CircleCI Server statefulsets to use the Bitnami Legacy repository.
All existing container images, including older or versioned tags, will be moved from the public catalog (docker.io/bitnami) to the Bitnami Legacy repository (docker.io/bitnamilegacy). This legacy catalog will receive no further updates or support and should only be used for temporary migration purposes.
Additional Notes:
CircleCI Server environments that were deployed using our air gapped installation procedure are not impacted.