All
Accepted answers
Steven LeBlanc · Oct 29, 2021 go to post

New builds with an extended key are now available from the InterSystems Container Registry. You can pull the new images as follows:

docker pull containers.intersystems.com/intersystems/iris-community:2021.1.0.215.3

docker pull containers.intersystems.com/intersystems/iris-community-arm64:2021.1.0.215.3

docker pull containers.intersystems.com/intersystems/irishealth-community:2021.1.0.215.3

docker pull containers.intersystems.com/intersystems/irishealth-community-arm64:2021.1.0.215.3

Steven LeBlanc · Sep 24, 2021 go to post

Hi Otto,

This appears to be a typo.  I've modified the marketplace listing and republished, which could take a few days to get approved. 

However, since this is a BYOL instance, once deployed it will just give you a VM which contains the IRIS for Health image, but no running container. The '1971' typo means that port 1971 is open to the VM in the firewall, but IRIS does not (yet) have any SuperServer port defined since it is not running. You could either start IRIS on 1971, or you could add a new firewall rule in GCP to open up port 1972 instead, in the meantime.

Thanks,

Steve

Steven LeBlanc · May 19, 2021 go to post

Hi David, yes I believe you'll need to contact the WRC to make sure that your email/login is linked to a supported organization, as that's required in order to access non-community images in the registry. You can contact support@intersystems.com and they can help straighten this out for you.

If you are otherwise intending to access Community Edition images, you shouldn't need to log in at all.

Steven LeBlanc · Apr 12, 2021 go to post

Hi Yuri,

This offer is not yet listed in the AWS Marketplace. It may be in the near future, but for now if you are interested in InterSystems concierge-level managed service for IRIS or IRIS for Health, please contact your account team.

Thanks,

Steve

Steven LeBlanc · Oct 16, 2020 go to post

Even after another docker logout? Please reach out to the WRC to help with your authentication issue. 

Steven LeBlanc · Oct 13, 2020 go to post

Hi, it's possible you're still logged into another registry. Can you try a 'docker logout' prior to attempting to access containers.intersystems.com?

Steven LeBlanc · Jul 2, 2020 go to post

As I understand, this functionality (as well as the ability to use default image tags such as 'openjdk' vs '/store/intersystems/...') is only available for Official Images (https://docs.docker.com/docker-hub/official_images/) that are published by Docker.  We are a verified publisher, and our images are Docker certified, but they are not published and maintained by Docker.

Steven LeBlanc · Jul 1, 2020 go to post

The Community Edition images for IRIS and IRIS for Health for ARM64 are now available in the Docker Store. Try them out!

InterSystems IRIS:

docker pull store/intersystems/iris-community-arm64:2020.2.0.211.0

InterSystems IRIS for Health:

docker pull store/intersystems/irishealth-community-arm64:2020.2.0.211.0
Steven LeBlanc · Jul 1, 2020 go to post

The Community Edition images for IRIS and IRIS for Health are now available in the Docker Store.  And we now offer the Community Edition for both x64 and ARM64 architectures. Try them out!

InterSystems IRIS:

docker pull store/intersystems/iris-community:2020.2.0.211.0
docker pull store/intersystems/iris-community-arm64:2020.2.0.211.0

InterSystems IRIS for Health:

docker pull store/intersystems/irishealth-community:2020.2.0.211.0 
docker pull store/intersystems/irishealth-community-arm64:2020.2.0.211.0
Steven LeBlanc · May 19, 2020 go to post

The preview builds have been updated to 204:

docker pull store/intersystems/iris-community:2020.2.0.204.0
docker pull store/intersystems/irishealth-community:2020.2.0.204.0
Steven LeBlanc · Apr 1, 2020 go to post

The Community Editions can also be found in the Docker Store: 

docker pull store/intersystems/iris-community:2020.1.0.215.0

docker pull store/intersystems/irishealth-community:2020.1.0.215.0
Steven LeBlanc · Mar 2, 2020 go to post

As of this release, it is only to be supported on Amazon EC2. Once there is a Community Edition image generally available... well I can't say it's supported on a Raspberry Pi but who am I to stop a tinkerer from tinkering...have fun! :-)

Steven LeBlanc · Mar 2, 2020 go to post

Hi Dmitriy,

Support for ARM64 architectures will initially be limited to Ubuntu-based containers only. I hope to have a preview image of InterSystems IRIS 2020.1 for ARM64 published in the AWS marketplace this week. This should run on the AWS Graviton based A1 instances now, and the M6g instances once they are generally available.

Thanks,

Steve

Steven LeBlanc · Feb 13, 2020 go to post

I've just uploaded the Community Editions to the Docker Store (2/13-updated with new preview build):

docker pull store/intersystems/iris-community:2020.1.0.199.0
docker pull store/intersystems/irishealth-community:2020.1.0.199.0
Steven LeBlanc · Jan 28, 2020 go to post

Yes, full kit versions of the 2020.1 Community Edition Preview are available through the WRC download site as well.

Steven LeBlanc · Dec 16, 2019 go to post

These are now available!

docker pull store/intersystems/iris-community:2019.4.0.383.0

docker pull store/intersystems/irishealth-community:2019.4.0.383.0
 

Steven LeBlanc · Nov 20, 2019 go to post

I think this would be much easier with BPL/DTL. Why not have your ObjectScript Business Process do its thing, then hand the result to a BPL to loop over OBRs and break it into multiple messages? Or put the BPL first, if your 'trickery' should happen to each generated message individually.

-Steve

Steven LeBlanc · Nov 5, 2019 go to post

I wasn't sure what RPMS was, but a Google search tells me it's an application for Indian Health Service. Are you trying to migrate the app from Caché to IRIS? Or is it already on IRIS and you want to know how to run it inside a Docker container? Or none of the above? The steps would be different depending on your answer.

Given that we're pretty far nested into a comment thread on an unrelated topic, I would recommend you either create a new DC post with more detail/background, or contact your Sales Engineer for advice on how to proceed with your migration or project.

Steve

Steven LeBlanc · Nov 4, 2019 go to post

Hi Stefan,

I believe Fabian was describing creating a new image, based off of the default InterSystems image, but modifying the user and group. (By the way, even though you are on Docker for Windows, InterSystems IRIS images are based on Ubuntu, and Docker for Windows runs in a Linux VM) The excerpt above would be placed in a new Dockerfile and you would build a new custom image. This approach is described here: https://irisdocs.intersystems.com/irislatest/csp/docbook/Doc.View.cls?KEY=ADOCK#ADOCK_iris_creating

However, may I ask, what version of InterSystems IRIS are you using? I have seen these "Sign-on inhibited" errors frequently in the past, but I think they've been mitigated in recent versions.  2019.3 was just released, and should be available in the Docker Store and cloud marketplaces in the next few days.

-Steve

Steven LeBlanc · Nov 4, 2019 go to post

Yes it does, IRIS includes interoperability, just without the healthcare-specific standards built in (HL7, FHIR, IHE, etc.)

Unhealthy, nice :-)

Steven LeBlanc · Nov 4, 2019 go to post

I'm not sure why that would be, and I'm not able to reproduce it.

The IRIS for Health Community instance on GCP has not yet been updated to the latest 2019.4 preview build. The standard IRIS Community instance has, and that appears to work out of the box for me. I'm told that the IRIS for Health listings should be updated in the next few days as well.

Steven LeBlanc · Nov 4, 2019 go to post

Strange... try logging in with: 

Username: _SYSTEM

Password: SYS

instead? Maybe you had a typo with your new password?

I'm not sure what else it could be. If this does not work, you may want to try blowing away the instance and launching a new one.

Steven LeBlanc · Nov 4, 2019 go to post

Hi Ignacio,

It looks like the container does not run automatically by the GCP launcher.  I was able to start it manually:

leblanc@intersystems-iris-health-community-editio-2-vm:~$ sudo docker ps -a
CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
leblanc@intersystems-iris-health-community-editio-2-vm:~$ sudo docker images
REPOSITORY                TAG                   IMAGE ID            CREATED             SIZE
intersystems/irishealth   2019.1.0S.111.0-gcp   a39d75e7a42b        9 months ago        1.61GB
leblanc@intersystems-iris-health-community-editio-2-vm:~$ sudo docker run -d -p 52773:52773 --name iris --init intersystems/irishealth:2019.1.0S.111.0-gcp
1932a6736c70d5e5dbd604b040f11907e8cdffa0aaccbbfce14bc37114c1ec46
 

Then I can launch the Management Portal, log in with SuperUser/SYS (then prompted to change my password), and use the instance.

I'll follow up internally to make sure the environment launches as intended, or at least see that the instructions are modified if this is how it is intended to work.

-Steve