Updating Docker images with new HCL Commerce releases

Updates for HCL Commerce runtime environments are delivered in releases as new Docker images. To update your runtime environment, you must download the new images, rebuild your custom images to include your custom code, and then deploy new containers.

It is recommended that one person in your organization complete this task and push the new Docker images to your private Docker registry. By doing so, the rest of your organization can simply pull the updated Docker images without having to rebuild with custom code.

HCL Commerce Version 9.1.14.0 or laterImportant: Beginning in HCL Commerce 9.1.14.0, application container images are built to be run as a non-root user by default. This change has the potential to break your custom deployment. Therefore, you must review this change and its potential impacts. For more information, see HCL Commerce container users and privileges.

Procedure

  1. Download the new Docker images.
  2. Set the spiuser password in the new Docker images.
    During the initial set up of your private Docker registry, you or an administrator should have already defined a Dockerfile that copies a custom custConfiguration.sh script that sets the spiuser password. Build new images by using the existing Dockerfile. Otherwise, recreate the files. For more information, see Setting the spiuser password in your Docker images.
  3. Deploy your existing custom code to the new Docker images.

Results

Your custom Docker images are updated. They now contain any changes and fixes that were specified in the update package provided by HCL. You must now deploy your new custom Docker images to your production environment to complete your site update.