It's not a big issue, to make it work. Just keep in mind that both containers, with SAM and monitored system, have to be in the same docker's network. If you run both images in with docker-compose, they by default will get the same network, so, in most cases, you may use IRIS service's name from docker-compose.yml as a hostname, and it will be able to connect to it internally inside that network.

If you need access from dockerized SAM to a dockerized IRIS, both working in different networks, you have to publish ports for IRIS, so, it should be available from the host, but from the docker, your SAM has to know the host's address and host.docker.internal is a way, to give it to him. And port should be the same as published when docker container is running.

When docker container is started with -p param, which says how to publish the port, possible to say, which IP to select, or select all  for instance -p 0.0.0.0:52273:52273

docker ps, may help with understanding how the container is available

8d8977f9d5f8   intersystemsdc/iris-community:preview                          "/tini -- /iris-main…"   6 days ago       Up 3 days (healthy)       0.0.0.0:1972->1972/tcp, 2188/tcp, 53773/tcp, 0.0.0.0:52773->52773/tcp, 54773/tcp                           iris

if it shows something like 127.0.0.1:52773->52773, it will only be available as localhost or 127.0.0.1 and will not be accessible from another container and network, because of host.docker.internal will refer to another ip

Could you explain, how you running all the parts?

There is a community edition license embedded, and you can use it.

The issue could be also, if you using some different user, set with USER line in Dockerfile, or with user parameter when you run it. The user running the IRIS inside the container should be irisowner.

There is was a change in users, and before starting a new container with durable %SYS, you have to change permissions. Look at the documentation

Globals are stored in the database and they are limited only by the size of that database.

I'm not sure if the size of the database has any limits, at all, but at least what I know, is that I have database files with up to 10 terabytes per one file. And the only reason is that it's not large than that, we split the data into smaller files due to external reasons, such as filesystems, and just having smaller files makes it easier to operate as a file.

The driver may work much faster when works locally, it uses shared memory for communication 

Is it works on the same host or not? Server and odbc  client

I've tested with a simple telnet client installed inside the container, and it works well.

activate Foreground in Production, and in the terminal, use the command

telnet localhost 63300

I working on macOS, and with docker. When I activate foreground, browser tries to execute telnet with this port. Did you try to expose port to the same one on the host, 63300:63300?

When you have ISFS configured to multiple namespaces, you can just use copy-paste ability to copy files between isfs folder, or with using real folder.

https://github.com/intersystems-community/iris-driver-distribution

Still the same, only offline mode will save it only locally and will not save on server.

Why you don't want to update the server?

Yeah, this is why you need to store files locally. And it's right.

But does not say why you need to work offline, how do you check if your code is working as expected?

So, it will be like offline mode, not just local mode. In this case, you may just deactivate the connection, with "objectscript.conn.active": false.

But, many features, which require an active connection to the server will not be available as well.

Just curious, what are the reasons to work this way?