0
0

Written by

Robert Cemper
~~ retired but not tired ~~
Follow
Question Robert Cemper · Nov 3

actual versions on intersystemsdc ?

#InterSystems IRIS #Docker

using  intersystemsdc/iris-ml-community:latest I failed with

Error: Invalid Community Edition license, may have exceeded core limit.
Shutting down the system : $zu(56,2)= 0Starting IRIS

What is the actual valid version with ML ??

Discussion (0)0
Log in or sign up to continue

Comments

Dmitry Maslennikov · Nov 3

Looks like ML edition is deprecated.
InterSystems removed them everywhere

Even for Enterprise most recent version is 2024.1

0
Robert Cemper  Nov 4 to Dmitry Maslennikov

Thank you @Dmitry Maslennikov !
You confirmed my initial suspicion.
And the missing intersystemsdc version (including preinstalled ZPM) 
affects a rather broad range of packages in OEX.

0
Gabriel Ing · Nov 4

You can still install the InterSystems AutoML onto the normal IRIS Community edition with a pip install - its difficult to find in the documentation but its this: 


```

python3 -m pip install --index-url https://registry.intersystems.com/pypi/simple --no-cache-dir --target /usr/irissys/mgr/python intersystems-iris-automl

```

That way you no longer need a specific ML docker image to use AutoML.

0
Robert Cemper  Nov 5 to Gabriel Ing

technically correct but not really a practical solution
for 50+ affected packages in  OEX  

0
Robert Cemper  Nov 9 to Evgeny Shvarov

That means that the -ml- versions are requested in Dockerfile or docker-compose.yml.
It is not immediately visible that ML is required and used.
For a few packages, it was pretty obvious that
it came in by cut&paste from previous packages..

0
Evgeny Shvarov  Nov 9 to Robert Cemper

It is also possible to install Python packages along with IPM via requirements.txt entry. In case it helps anyhow.

0
Robert Cemper  Nov 9 to Evgeny Shvarov

Yeah!
If there is a reference of how to add -ml- functionality to available intersystemsds/iris-community and intersystemsdc/irishealth-community 
The other possibility could be to change to NON-intersystemsdc versions
and add the single-line installation for ZPM.  Not my favorite.  

0
Robert Cemper  Nov 9 to Robert Cemper

Hi @Evgeny Shvarov 
You inspired me to extend the standard Dockerfile sequence by this line

RUN --mount=type=bind,src=.,dst=. \
    iris start IRIS && \
    iris session IRIS < zpm.script && \
    iris session IRIS < iris.script && \
    iris stop IRIS quietly

and zpm.script is basically the version-independent one-liner sliced to readable pieces

zn "%SYS"
 ;; from onezpm
hang 3
write !,"from onezpm",!
set r=##class(%Net.HttpRequest).%New()
set r.Server="pm.community.intersystems.com"
set r.SSLConfiguration="ISC.FeatureTracker.SSL.Config"
do r.Get("/packages/zpm/latest/installer")
do $system.OBJ.LoadStream(r.HttpResponse.Data,"c")
ZPM "repo -r -n registry -url https://pm.community.intersystems.com/ -user """" -pass """""
zpm "enable -community"
hang 2
Write !,"ZPM ready",!
halt

This makes me independent from the limits of intersystemsdc/.....
and I can use images from 
containers.intersystems.com/intersystems/****-community
with a minimal invasive approach without touching any other part of the repo

0
Evgeny Shvarov  Nov 10 to Robert Cemper

Yes. The initial idea for intersystemsdc was to avoid waiting on the Docker build process to install IPM and other syntax sugar and good stuff from OEX.

So, maybe we don't need intersystemsdc now very much to always get along with official containers set.

0
Robert Cemper  Nov 9 to Zion Amsalem

In most cases, I've seen working before
the real message was "community license expired."
You see it only in the builder log. OR
using  docker compose --progress plain build  from command line.
workaround:
use instead.  intersystemsds/iris-community or intersystemsdc/irishealth-community  
:latest is always the default

0