I'm interested to hear if folks have experience using Docker containers with Caché instances using ECP. Wondering if there are any special considerations when setting up a distributed application with multiple containers communicating with ECP. Any input is appreciated!
I found the need to merge 2 Docker images (e.g. intersystems/iris-community:2020.2.0.199.0 + my home grown NodeJS Image). I found some advice on the Web but no real convincing solution.
Working from home during these Corona-days I'm short on resources. - no Linux machine available - limited disk space So I decided to give Docker in Windows 10 (named Docker Desktop) a try.
Hello Everyone, I am new here and I am learning docker to crack my upcoming interviews. I am confused whats the steps in a deploy process for Dockerized Apps stored In A Git Repo? I am so confused about this, Can anyone know about docker programming. If yes then please suggest some more tips which are useful for my future point.
I've been working on deploying an IRIS for Health environment in EKS. There is a video session in the InterSystems learning portal about this feature but I have not succeeded in finding the proper documentation and resources to use this in my Kubernetes cluster.
Has this been deprecated/discontinued? Any idea where can I find the resources? Should I stick to StatefulSets instead of using the IrisCluster resource type provided by this operator?
I've always worked with typical web applications (a bunch of code files that sit in a server that connects to an RDS). Now our team is responsible for different IRIS for Health environments. We are currently working to set up the local dev environment and this is the current scenario:
* IRIS for Health local development server is running in a container
* Developers are using VSCode with the objectScript plugin
* GitHub as a version control system for the code and configuration.
For example, let's use this template repo. If you build this container A using docker-compose and then run the container it exposes REST-API which is available on:
localhost:52773/person/all
The question is how to make this REST-API accessible from another docker container B running on the same machine? E.g. with IRIS 2019.4 Community from this repo?
The problem is that for the second container localhost it's something which belongs to container B.
I think I need to set up a network between containers somehow. E.g. using docker-compose. But is there any simpler way?
I thought I test the InterSystems IRIS for Health 2020.1, the Docker image. but for some reason, the container only lives for about 10 seconds and I can see from the message.log file that as soon as IRIS starts it then performs shutdown thus ending also container. Anyone else seen this?
Hi all, I'm having issues with mounting custom database on top of IRISHealth 2019.1 docker container. Data gets mounted only in Read-only mode. This means read operations are successful but I couldn't make the image with databases mounted in Read/write, both modes. Is anyone having similar issue?
I want to add ports 9100 and 9101 in addition to 52773. I read on docker container documentation that this is not possible on a already ran image. Currently it starts the google cloud IRIS health container automatically without me able to specify the additional ports. How can I add ports to Google cloud IRIS Health container?
When deploying IRIS in a container, what are recommendations for permitting users terminal access? There is docker exec -it, but that does not work from a user's workstation where - in the old deployment model - they would connect to the server over ssh using Putty and open a terminal session from there.
I started to play with docker and InterSystems products, it's amazing, but I got the error when try to load the IAM-0.34-1-1.tar.gz image to docker:
[root@CONF-RHEL-DOCKER-IRIS-API admconf]# docker load -i IAM-0.34-1-1.tar.gz open /var/lib/docker/tmp/docker-import-547148651/IAM/json: no such file or directory
Bellow docker and docker-compose version:
[root@CONF-RHEL-DOCKER-IRIS-API admconf]# docker --version Docker version 19.03.2, build 6a30dfc
IRIS offers Durable %SYS Directory as a highly useful feature for working with containers.
Before inventing the wheel once more I'd like to know if a similar feature also exists for Caché / Ensemble. Official documentation is quite silent about. Though I have some names in mind that might know more about ( @Luca Ravazzolo? @Dmitry Maslennikov ? @Eduard Lebedyuk ? )
OAuth server to be deployed on the IRIS learning cloud platform. Clients - one on the other instance of the learning IRIS server, the other client locally on my computer in the container docker.
Both clients get a seemingly correct link (through ##class(%SYS.OAuth2.Authorization).GetAuthorizationCodeEndpoint()) to the login request form:
Every day coding with IRIS and docker I call the following 3 commands in VSCode terminal. Always the same for any projects:
docker-compose build ; to build the container
docker-compose up -d ; to run the IRIS in container
docker-compose exec iris iris session iris ; to open the IRIS terminal
Is there any way to map the key sequence which will type me the rest?
I am trying to experiment the Docker container in our development environment. I have successfully build an image and running the container. When I access the CSP portal home page ( http://<host-ip>:57772/csp/sys/%25CSP.Portal.Home.zen?$NAMESPACE=%25SYS), I am getting the following error:
I am having some issues creating a docker image with a fresh cache installation. The error that I am getting right now is that gzip is required for a cache installation, but was not found in my system. Even though, this is shown as installed in the base centos 7 image. My host machine is Windows 10 using the latest docker version.
Just got the new beta version of Docker, with depreciation warning of AUFS. It's so bad news when InterSystems does not support used by default storage driver overlay2. Recently I thought to play with Google Kubernetes Engine, and realized that I can't work with InterSystems products there due to incompatibility with Storage Driver. Maybe it's already time to think about support?
i've been trying to setup a copy of our production server so we can use it for testing/development.
i did a full backup. moved it to the new server. ran the DBREST command. got it to restore but seems like permissions get all messed up. and it just generates a bunch of errors.
How suitable is Docker for standalone deployment of an Ensemble version and Ensemble application together?
The context is deployment by an application partner of an integration application and the supporting Ensemble version as a single package (single file ideally), to multiple environments and to multiple customer sites.
I don't have experience with Ensemble on Docker so I'm wondering what gaps and pitfalls may exist.
By update
