Just to clarify again - these types of issues are not related to ZPM anyhow.

But yes - this happens with docker sometimes, it's a "dark side" of docker-way of software development ;) If something doesn't work without a reason every time I do the following:

1) build without cache:

docker-compose build --no-cache

2) clean up docker:

docker system prune -f

In a lot of cases, this helps.

And maybe it's a trigger for us to make docker images smaller, @Steven LeBlanc , @Luca Ravazzolo ?

Another approach is not having docker locally at all - e.g. Github Codespaces very promising way forward, you code in a browser and use Github's docker infrastructure (which is endless?).

Another idea - your docker just doesn't have enough resources for this. I have 6GB memory and 200G space.

Just tested on 2020.4 zpm enabled:

HSLIB>DO ##class(HS.HC.Util.Installer).InstallFoundation("HSFOUNDATION")


HS.Util.Installer.Foundation:Install User 'irisowner' has %Admin_Manage:USE privilege

HS.Util.Installer.Foundation:Install tComponent Foundation = HSFOUNDATION

HS.Util.Installer.Foundation:Install About to Create Database HSFOUNDATION

HS.Util.Installer.Foundation:Install Create IRIS.DAT in HSFOUNDATION

HS.Util.Installer.Foundation:Install Made Namespace HSFOUNDATION

HS.HC.Util.Installer:EnableEnsemble Created Ensemble Mappings

HS.HC.Util.Installer:EnableEnsemble Configuration Loaded

HS.HC.Util.Installer:EnableEnsemble Compiling Ensemble DeepSee Dashboard

HS.HC.Util.Installer:EnableEnsemble Ensemble Enabled

HS.Util.Installer.Foundation:SecureInstall Added Package mappings HS,HSMOD,SchemaMap

HS.Util.Installer.Foundation:SecureInstall Added include mappings HSMOD.*,SchemaMap*

HS.Util.Installer.Foundation:Install Created Portal CSP app

HS.Util.Installer.Foundation:CreateProduction Compiled template HSFOUNDATIONPKG.FoundationProduction

HS.Util.Installer.Foundation:AdditionalSetup Set Credential HS_Services

Running HS.Util.Installer.Kit.PostInstall.SetupOIDRegistry:RunHub(HSFOUNDATION) 

Ran HS.Util.Installer.Kit.PostInstall.SetupOIDRegistry:RunHub with status OK

Running HS.Util.Installer.Kit.PostInstall.AssignAuthTypes:RunHub(HSFOUNDATION) 

Ran HS.Util.Installer.Kit.PostInstall.AssignAuthTypes:RunHub with status OK

HS.Util.Installer.Foundation:SecureInstall Recompiled XML extension classesSaving hl7.fhir.r3.core@3.0.2

Saving hl7.fhir.r4.core@4.0.1

Saving hl7.fhir.us.core@3.1.0

Load Resources: hl7.fhir.r3.core@3.0.2

Load Resources: hl7.fhir.r4.core@4.0.1

Resource Used in Multiple Packages: http://healthit.gov/nhin/purposeofuse|2.0(hl7.fhir.r3.core@3.0.2,hl7.fhir.r4.core@4.0.1)

Resource Used in Multiple Packages: http://dicom.nema.org/resources/ontology/DCM|01(hl7.fhir.r3.core@3.0.2,hl7.fhir.r4.core@4.0.1)

Load Resources: hl7.fhir.us.core@3.1.0


HS.FHIRServer.Installer:InstallNamespace Created FHIR web application

HS.FHIRServer.Installer:InstallNamespace Created FHIR API web application

Load of directory started on 11/04/2020 08:59:25


Loading file /usr/irissys/dev/fhir/gbl/XFReferenceField.xml as xml

Imported global: ^HS.XF.ReferenceField

Loading file /usr/irissys/dev/fhir/gbl/XFTransform.xml as xml

Imported global: ^HS.XF.Transform

Loading file /usr/irissys/dev/fhir/gbl/XFValueSet.xml as xml

Imported global: ^HS.XF.ValueSet

Loading file /usr/irissys/dev/fhir/gbl/XFConfig.xml as xml

Imported global: ^HS.XF.Config

Loading file /usr/irissys/dev/fhir/gbl/XFReferenceType.xml as xml

Imported global: ^HS.XF.ReferenceType

Load finished successfully.


HS.Util.Installer.Foundation:SecureInstall Install HSFOUNDATION done at 2020-11-04 08:59:26

HSLIB>w $zv

IRIS for UNIX (Ubuntu Server LTS for x86-64 Containers) 2020.4 (Build 524U) Thu Oct 22 2020 13:04:25 EDT

HSLIB>zpm

zpm: HSLIB>version


%SYS> zpm 0.2.8

 Locally installed zpm-registry not found

https://pm.community.intersystems.com - 0.0.2

zpm: HSLIB>

It works.  I guess the issue is with your docker, it could run out of resources.

@Steve Pisani, if you perform docker cleanup (it's safe):

docker system prune -f

and test again?

Thanks, Steve! Just to clarify: this issue is related to ZPM-enabled IRIS for Health images, right? Filed the issue.

You also can check direct messages here on DC - if people click the I'm Interested button you'll get a direct message.

ZPM images are updated with a new IRIS 2020.4.0.524.0 build.

I think maven is great, looking forward to hearing the news from @Bob Kuszewski 

Double copy-n-paste. Fixed the link.

If we host it in the repository until it'd be published on maven, will it solve the issue temporarily? Like here.

Technology bonuses for the interoperability contest

We added an IRIS Interoperability Template with a very simple (the simplest probably) but working template of an IRIS Interop production

Also, check my session Creating InterSystems IRIS Analytics Solutions Using Docker & VSCode

The related code could be found here on Github.

Sure. PEX demo is included in examples list, thanks @Eduard Lebedyuk 

Thanks again, Guillaume!

fixed! 

And we updated the images with ZPM 0.2.7 too:

intersystemsdc/iris-community:2020.3.0.221.0-zpm

intersystemsdc/iris-community:2020.4.0.524.0-zpm

intersystemsdc/iris-ml-community:2020.3.0.302.0-zpm

intersystemsdc/irishealth-community:2020.3.0.221.0-zpm

intersystemsdc/irishealth-community:2020.4.0.524.0-zpm

intersystemsdc/iris-community-arm64:2020.4.0.524.0-zpm

intersystemsdc/irishealth-community-arm64:2020.4.0.524.0-zpm

And to launch IRIS do:

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community:2020.3.0.221.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community:2020.4.0.524.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-ml-community:2020.3.0.302.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community:2020.3.0.221.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community:2020.4.0.524.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/iris-community-arm64:2020.4.0.524.0-zpm

docker run --rm --name my-iris -d --publish 9091:1972 --publish 9092:52773 intersystemsdc/irishealth-community-arm64:2020.4.0.524.0-zpm 

And for terminal do:

docker exec -it my-iris iris session IRIS

and to start the control panel:

http://localhost:9092/csp/sys/UtilHome.csp

To stop and destroy container do:

docker stop my-iris

While we are building a maven distribution channel the latest IRIS JDBC driver could be downloaded from here

If you are on VSCode try SQL Tools InterSystems addon - it has schema code completion. Is this what you are looking for?