Recent posts:
Recent replies:

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

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

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.

Open Exchange applications:
Followers:
Following:
Steven has not followed anybody yet.
Global Masters badges:
Steven has no Global Masters badges yet.