actual versions on intersystemsdc ?
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 ??
Comments
Looks like ML edition is deprecated.
InterSystems removed them everywhere.png)
Even for Enterprise most recent version is 2024.1.png)
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.
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.
technically correct but not really a practical solution
for 50+ affected packages in OEX
We have 50+ packages on IntegratedML on OEX? wow. @Thomas Dyar
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..
It is also possible to install Python packages along with IPM via requirements.txt entry. In case it helps anyhow.
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.
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 quietlyand 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",!
haltThis 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
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.
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
I've updated the building process. Now should get updates at least in one day after official release.
And returned ML version, even when there is no official build.
Big THANKS!
A great improvement!
Especially useful for continuous repeating quality checks in OEX !
Greetings Robert! Is there a Doc or training that can help me learn about using:
1. Allow the Access gateways to receive the REST traffic
2. Modify the Access gateways Production to identify if a query is supposed to be a single site query (station ID in path url) or a multi-site query (all sites listed in JSON request body where it should be invoked)
any help is appreciated! -Anthony
sorry, I'm no expert on those subjects