In case you're planning on deploying IRIS For Health, or any of our containerized products, via the IKO on OpenShift, I wanted to share some of the hurdles we had to overcome.

As with any IKO based installation, we first need to deploy the IKO itself. However we were getting this error:

Warning FailedCreate 75s (x16 over 3m59s) replicaset-controller Error creating: pods "intersystems-iris-operator-amd-f6757dcc-" is forbidden: unable to validate against any security context constraint:

proceeded by a list of all the security context constraints (SCCs) it could not validate against.

If you're like

I want to address the nasty problems about reading a flat text in ASCII, UTF*
explicitly excluding HTML, EBCDIC, and other encoding.
According to Wikipedia there are at least 8 variations of control characters.

• CR+LF is typical for Windows
• LF is typical for the Linux/UNIX world
• CR is Mac's favorite

As you can deduct from the names the inspiration comes from mechanical typewriters.

In IRIS* similar as in Caché or Ensemble or ... the classes %Stream* and %File* offer
the same property with the same default 
• property LineTerminator as %String(MAXLEN=10) [ InitialExpression =

I downloaded containers.intersystems.com/intersystems/healthshare_providerdirectory:2023.2 to evaluate, however when I try to run the container it keeps

exiting. 

>docker run --name providerdirectory --user=irisowner --env=ISC_DATA_DIRECTORY=/intersystems/irisdata --runtime=runc -d containers.intersystems.com/intersystems/healthshare_providerdirectory:2023.2

I keep getting the following, and I am not sure why...

2024-01-1720:36:20 [INFO] Executing command /home/irisowner/irissys/startISCAgent.sh 2188...
2024-01-1720:36:20 [INFO] Writing status to file: /home/irisowner/irissys/iscagent.status
2

I have been struggling with a docker run command that kept crashing, the error message was too generic to point me to the right direction.

Since the container is shut down after the failure, I was unable to login to it in order to figure out the problem.

I had to run the container in a way that I'll be able to log into it before it crashed, so I found the adding  -u false prevents the docker run command to run the iris session IRIS and the container stayed up and running. then I was able to log into it using:

docker exec -it <container id / name> /bin/bash

inside the container I was able to try

Hello,

I've been running IRIS in a container for a while with the durable %SYS feature. Previously, I was running IRIS 2022.x version and decided to upgrade to 2023.1. During image build, I create some namespaces and install a FHIR repo into one of them using the following script:

Do ##class(HS.FHIRServer.Installer).InstallNamespace()
Do ##class(HS.FHIRServer.Installer).InstallInstance(appKey, strategyClass, metadataPackages)

However, when I updated the container (stopped the existing one, started the new one), I noticed a peculiar error.

We are using IRIS health 2023.1 to build an application that runs on kubernetes cluster as container images. In the container image, we have our own PRODUCTION "APP" created with its routines database and global database located at:

/usr/irissys/mgr/APPCODE/IRIS.DAT

/usr/irissys/mgr/APPDATA/IRIS.DAT

To persist the data, we use the “Durable %SYS for Persistent” featureand set the ISC_DATA_DIRECTORY to an external durable folder (/durable/iconfig).

However, we encounter a problem when we try to upgrade the application:

1. We deploy the initial version of the application image at the customer site,

Is it possible to add the intersystems registry (https://containers.intersystems.com/) in portainer with authentication ?

In this series of articles, I'd like to present and discuss several possible approaches toward software development with InterSystems technologies and GitLab. I will cover such topics as:

• Git 101
• Git flow (development process)
• GitLab installation
• GitLab Workflow
• Continuous Delivery
• GitLab installation and configuration
• GitLab CI/CD
• Why containers?
• Containers infrastructure
• CD using containers
• CD using ICM
• Container architecture

In this article, we would talk about building your own container and deploying it.

Hi Developers,

Dive into the latest video on InterSystems Developers YouTube:

⏯ Working with Containers & InterSystems Technology @ Global Summit 2023

I'm trying to run IRIS for Health Community Edition container on Mac (Apple chip) as follows

docker run --name iris -d --publish 1972:1972 --publish 52773:52773 --volume /<volume-path-on-host>:/<volume-name-in-container> --env ISC_DATA_DIRECTORY=/<volume-name-in-container>/<durable-directory> containers.intersystems.com/intersystems/irishealth-community-arm64:latest-cd

but it will error out to start

2023-10-1709:15:2910/17/23-13:15:29:045 (391) 0 [Utility.Event] Updating configuration files
2023-10-1709:15:2910/17/23-13:15:29:219 (391) 0 [Utility.Event] Creating directory

For containers in ECS files are not editable if the file size is larger than ephemeral storage free space. For example if I have 4Gb free I can't edit 8Gb file. But if I start container with 50 Gb of ephemeral storage (24Gb free) I can edit my 8Gb file just fine. Even file attributes cannot be changed: chattr -i <file> fails if the amount of free ephemeral storage is not enough (and so db can't be mounted for writing).

This can cause iris container failure on startup if large DB is both RW and mounted on start.

I think there have been articles published here before but I'm struggling to find them:

I'd like to be able to create my own customised version of the official IRIS Community Edition Container, eg with Node.js and a number of modules pre-installed.  So, for example, can I create my own Dockerfile that begins with something like:

         FROM containers.intersystems.com/intersystems/iris-community-arm64:2023.2.0.227.0

and then I can add my own stuff to it?

... or is there another recommended approach?

Any info appreciated

What's the way to get healthcheck info for an IRIS (container) running without PWS?

I've tried to access this morning at https://containers.intersystems.com/contents and I'm receiveing a 503 as answer.

Come on! I need my dosis of IRIS + Docker!

Hi Community,

In my previous article, we learned topics listed below:

1. What is Docker?
2. Some of the Docker benefits
3. How does Docker work?
4. Docker Image
5. Docker Container
6. Docker Image repository
7. InterSystems's Docker image repository
8. Docker Installation
9. Docker Basic Commands
10. Running IRIS community edition by using Docker
11. Docker Desktop GUI

In this article, we will cover the following topics:

1. Use of Docker Compose file (a YAML file)
2. Use of Docker file (employed to build a Docker image)
3. Use of Docker volume

So let's begin.

Hi All,

Been trying to setup a iris 4 health community version along with a webgateway bothing utilizing docker. The documentation seems a little sparse when it comes to configuring each of these to work together, especially when it comes to utilizing the Webgateway to front end the MGMT pages for Irirs 4 Health.

I know there is a github repo that has a docker compose file, but that doesn't see to provide a light on what needs to be configured in order for it to work.

I know that the community version still includes a PWS but as a developer, I'd like to mock a production environment as closely

In this series of articles, I'd like to present and discuss several possible approaches toward software development with InterSystems technologies and GitLab. I will cover such topics as:

• Git 101
• Git flow (development process)
• GitLab installation
• GitLab Workflow
• Continuous Delivery
• GitLab installation and configuration
• GitLab CI/CD
• Why containers?
• Containers infrastructure
• CD using containers

In the first article, we covered Git basics, why a high-level understanding of Git concepts is important for modern software development, and how Git can be used to develop software.

In the second article, we covered GitLab Workflow - a complete software life cycle process and Continuous Delivery.

In the third article, we covered GitLab installation and configuration and connecting your environments to GitLab

In the fourth article, we wrote a CD configuration.

In the fifth article, we talked about containers and how (and why) they can be used.

In the sixth article let's discuss main components you'll need to run a continuous delivery pipeline with containers and how they all work together.

In this article, we'll build Continuous Delivery configuration discussed in the previous articles.

InterSystems has also released IRIS as containerized deployments. This post is to demonstrate how InterSystems IRIS and applications those rely on IRIS a backend can be packaged into an image and be run in other machines in containers and how simple it is to do that.

A container runs image/s which have all the necessary executables, binary code, libraries, and configuration files. And the images can be moved from one machine to another, and  an images repository like Docker Hub can simplify that process.

I have used an application from Open Exchange for this demo.

Demo video: https://www.loom.com

Have Docker running in Ubuntu and successfully downloaded IRIS Healthcare ML Community to local machine.

Cannot figure out how to launch IRIS...help!

Thanks, all...

Martin Arnold

Hi community members!

I'm trying to deploy a container based on IRIS Community for Health ML image available from this url but when I start the container the memory consumption skyrockets to 99% making impossible to work with the instance (it never goes below the 95% of the memory). When I do the same with the IRIS Community for Health image it never goes over 80% of memory.

Is this a known problem? Should I try another version? Maybe have I just to sit down in a corner and cry like a baby?

i tried to install SAM 2.0.1. on a redhat 8 server.

i use docker for managing the containers.

I have followed the documentation for the installation and deployment of SAM step by step

when trying to start the SAM with the script i have an container that can't be created and the prompt not responding 

must kill the process to stop .

Does anyone have an idea?

Has anyone seen this before? I'm new/bad at Docker and not even sure how to debug.

$ sudo docker logs <container>
[INFO] Starting InterSystems IRIS instance IRIS...
[INFO] Unable to read the startup.last file to identify the location of the write
image journal file (IRIS.WIJ) that was last in use by this instance. Please
fix the permissions of the startup.last file.

** Startup aborted **

Starting IRIS
Recovery failure. Startup aborted.
[ERROR] Command "iris start IRIS quietly" exited with status 256
[ERROR] See the above messages or /usr/irissys/mgr/messages.log for more information
[FATAL] Error

The Amazon Web Services (AWS) Cloud provides a broad set of infrastructure services, such as compute resources, storage options, and networking that are delivered as a utility: on-demand, available in seconds, with pay-as-you-go pricing. New services can be provisioned quickly, without upfront capital expense. This allows enterprises, start-ups, small and medium-sized businesses, and customers in the public sector to access the building blocks they need to respond quickly to changing business requirements.

Updated: 10-Jan, 2023 

Hi Community!

I think everyone keeps the source code of the project in the repository nowadays: Github, GitLab, bitbucket, etc. Same for InterSystems IRIS projects  check any on Open Exchange.

What do we do every time when start or continue working with a certain repository with InterSystems Data Platform?

We need a local InterSystems IRIS machine, have the environment for the project set up and the source code imported.

So every developer performs the following:

1. Check out the code from repo
2. Install/Run local IRIS installation
3. Create a new namespace/database for a project
4. Import the code into this new namespace
5. Setup all the rest environment
6. Start/continue coding the project 

If you dockerize your repository this steps line could be shortened to this 3 steps:

1. Check out the code from repo
2. Run docker-compose build 
3. Start/continue coding the project 

Profit - no any hands-on for 3-4-5 steps which could take minutes and bring head ache sometime.

You can dockerize (almost) any your InterSystems repo with a few following steps. Let’s go!

Hi Developers,

Enjoy watching the new video on InterSystems Developers YouTube:

⏯ InterSystems Deployment Options @ Global Summit 2022

Such most popular nowadays CI platforms as GitHub and Gitlab, offers the ability to run any docker image as a service, mostly useful for integration tests.

And I could define a GitHub workflow like this for instance, for some of my Python project which, requires the connection to IRIS

name:IRIScontainerexampleon:pushjobs:# Label of the container job  container-job:# Containers must run in Linux based operating systems    runs-on:ubuntu-latest# Docker Hub image that `container-job` executes in    container:python:310# Service containers to run with

Does anyone have experience with installing the Arbiter Container using Podman instead of Docker in a Red Hat environment? I was able to pull down the docker image, but unsure what are the next steps as I am confused on how to start the container using Podman and ensure the parameters are set appropriately? Does anyone have the steps that I should take? Should I go through the WRC? Does the WRC have experience using Podman?

Or should I just install the ISC Agent instead of using the Container?

Please and thanks,

Scott Roth

My team works on implementing an Interoperability solution utilizing InterSystems Kubernetes Operator on Red Hat OpenShift container platform. 

We are trying to determine how many messages we can process in any given time. We have a Feeder app running in 10 containers sending 50k messages each to a load balancer all beginning at the same time.

Messages are received via HTTPS protocol by webgateway containers. 

Interoperability production runs in compute pods with persistent data, journals, and WIJ volumes.

We implemented Horizontal Pod Autoscaler to scale compute pods when CPU utilization is high.

Announcing the InterSystems Container Registry web user interface

InterSystems is pleased to announce the release of the InterSystems Container Registry web user interface. This tool is designed to make it easier to discover, access, and use the many Container images hosted on ICR.

The InterSystems Container Registry UI is available at: https://containers.intersystems.com/contents

Community Edition Containers

When you visit the ICR user interface, you’ll have access to InterSystems' publicly available containers, including the IRIS community edition containers.

Hi Community,

Watch this video to get a brief overview of the near- and long-term plans for HealthShare containerization and Kubernetes adoption, as well as a preview/demo of our current progress.

⏯ The Future of HealthShare in the Cloud: Containers/ Kubernetes @ Global Summit 2022