On AIX, the OpenSSL package that comes with AIX is structured differently than in other operating systems.  The OpenSSL 3.x package comes with implementations of OpenSSL 1.0.2, 1.1.1, and 3.0.  Sadly, the OpenSSL 3.0 implementation which is included in AIX 7.3 TL1 is missing a few features that are critical to correct operation with IRIS.  So, currently versions of IRIS use the OpenSSL 1.0.2 implementation.  IBM is readying their updated package with the fixes to the OpenSSL 3.0 implementation included.

The plan for new IRIS containers is to use YYYY.R format only.  Let's walk through an example of a few releases for a hypothetical IRIS 2024.1 release.

Release Old Tag New Tag
Initial GA 2024. 2024.1
First maintenance 2024. 2024.1
Security Fix 2024. 2024.1

This new scheme greatly simplifies your work to keep up with whatever mix of maintenance and security releases we provide.  All you need to do is reference iris:2024.1 and you'll pick up the latest bug and security fixes without making any changes to your code.

As for the latest tag, we like the idea so much that we're giving you two.  One that lets you get the latest release (iris:latest-cd) and one that lets you get the latest long-term-support release (iris:latest-em).  

Excellent article!  

A note for people using Kubernetes or Containers in the cloud:   This same advice applies for Kubernetes-based and containers-based deployments.  When you create a Kubernetes cluster you assign VM resources (NodeGroups, for example) and you'll want to use the advice in this article to create the right nodes and storageclass for your deployment.

If you choose to create your own container for C/E, you're responsible for the container and for how it interacts with the host operating system. For example, InterSystems can't give you assistance with creating your Dockerfile or debugging any problems you might have with the container-storage interface. We will, of course, continue to support your usage of C/E. For example, questions about monitoring your queues or creating business operations. If you have detailed questions, please reach out to me.

Telling you something you already know:  You've got some bad state in your container image or in the persistent storage. 

I think we'd need to see more to be able to help:
* What's the command you're using to run the container?  All the environment variables and mount points is super-important here
* What's the container you're running?  If its your own, maybe the Dockerfile would help

Here's an example I had put together in a different context.  It sets up a single IRIS instance with a WebGateway and IAM.  It also sets up TLS on the IAM instance.

apiVersion: intersystems.com/v1alpha1
kind: IrisCluster
  name: fhir-iam
    - name: icr-secret
  storageClassName: gp2
    name: fhir-iris-key-secret
    name: fhir-iris-cpf
        secretName: fhir-iam-tls
      image: containers.intersystems.com/intersystems/iam:
      image: containers.intersystems.com/intersystems/webgateway:2022.
      type: apache
      replicas: 1
        - /csp/sys
        - /myfhirserver
        - /csp/healthshare
      alternativeServers: LoadBalancing
      image: containers.intersystems.com/intersystems/irishealth:2022.
      type: ClusterIP