Update Bitnami image references

Changes have been announced for the Bitnami public catalog that will affect Bitnami images used by Commerce. To avoid service interruptions, immediately download the Bitnami images used by Commerce to your own Docker repository.

Impact on HCL Commerce

The Bitnami public catalog has changed. The following Bitnami images are included in the Redis and Zookeeper Helm charts that are bundled with HCL Commerce Version 9.1 by default:

  • bitnami/redis – used for caching

  • bitnami/zookeeper – used for Elasticsearch

If you are using a Bitnami Helm chart to set up Postgres database for your approval server → Reference

If you are configuring centralized logging → Reference

As the changes are implemented, these images may fail to restart or redeploy. This update impacts all environments, including production.

If your deployment does not use any of the above Bitnami Docker images, you are not impacted by this change, and no action is required.

Action required

Note: Perform this action in your development or testing environment first, before you update your production environment.
  1. Download the Bitnami images that you use, and push them to your organization’s private repository.
    Note: As a temporary or emergency workaround, you can use the Bitnami Legacy repository to re-enable a site. Ensure the version of the images you are using are available in the Bitnami Legacy repository before choosing this approach. Use the Bitnami Legacy repository.
  2. Update the Bitnami Docker image repository references in the following configuration files.
    • HCL Commerce Devops: env.sh
    • HCL Commerce Helm Charts: values.yaml
  3. For Helm chart deployments, set allowInsecureImages to true for the Bitnami service.
    For Helm chart deployments, set allowInsecureImages to true for the Bitnami service.
  4. For helmchart, run the helm upgrade command to redeploy Bitnami containers from the new Docker repository. For docker-compose, redeploy Bitnami containers with the new Docker repository.

Example: Updating Redis

  1. Push the appropriate Redis image to your own Docker repository.
    docker pull bitnami/redis:7.4.2-debian-12-r6
docker tag bitnami/redis:7.4.2-debian-12-r6 docker.io.mycompany.com/bitnami/redis:7.4.2-debian-12-r6
docker push docker.io.mycompany.com/bitnami/redis:7.4.2-debian-12-r6
  2. Update the helmchart values.yaml configuration file to point to the new repository.
    redis:
  image:
    registry: docker.io.mycompany.com
    repository: bitnami/redis
    tag: 7.4.2-debian-12-r6
  3. Update the Helm chart values.yaml to set allowInsecureImages to true:
    redis:
  global:
    security:
      allowInsecureImages: true
  4. Run the helm upgrade command to deploy the Bitnami containers with the image in the new repository. Doing this will trigger a rolling update.