Containerization is a lightweight alternative to full machine virtualization that involves encapsulating an application in a container with its own operating environment.
If you do not have direct access to the server that runs your IRIS Docker container you still may require access to the container outside "iris session" or "WebTerminal". With an SSH terminal (PuTTY, KiTTY,.. ) you get access inside Docker, and then, depending on your needs you run "iris session iris" or display/manipulate files directly.
Note:
This is not meant to be the default access for the average application user but the emergency backdoor for System Management, Support, and Development.
Is there an InterSystems supported dotnet core library or community contributed repo on the horizon? At this time we are exploring installing the ODBC driver in our containers but would rather use more robust solution.
We're pleased to announce that that InterSystems IRIS Community Edition is available on the Docker Store! InterSystems IRIS Community Edition is the no-cost developer edition designed to lower the barriers to entry to get started with IRIS. Now that it is listed on the Docker Store, running an IRIS Community instance is as easy as -
In this series of articles, I'd like to present and discuss several possible approaches toward software development with InterSystems technologies and GitLab. I will cover such topics as:
Git 101
Git flow (development process)
GitLab installation
GitLab Workflow
Continuous Delivery
GitLab installation and configuration
GitLab CI/CD
Why containers?
Containers infrastructure
CD using containers
CD using ICM
Container architecture
In this article, we would talk about building your own container and deploying it.
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.
I am new to using containers. I am working on trying to specify some of the SAM settings and wondered how to access the terminal while IRIS is running in a Container. Can someone help me out?
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.
We are using IRIS health 2023.1 to build an application that runs on kubernetes cluster as container images. In the container image, we have our own PRODUCTION "APP" created with its routines database and global database located at:
Docker 20.10.14 (released March 23, 2022) changes the Linux capabilities given to containers in a manner that is incompatible with the Linux capability checker in InterSystems IRIS 2021.1 (and up) containers.
Users running Docker 20.10.14 on Linux will find that IRIS 2021.1+ containers will fail to start and the logs will incorrectly report that required Linux capabilities are missing. For example:
For quite some time InterSystems IRIS supports such thing as Merging CPF. So, with help of this it should be possible to define only desired changes in configuration. And get them applied even with vanilla Docker image.
And I though it could be useful when used with Dockerfile. Use this way to configure IRIS during docker build instead of using Installer manifest.
After attending the Intersystems DACH conference in Germany at the end of last November and taking part in a few workshops about containers and microservices I took the plunge and installed Docker on home Windows PC, downloaded IRIS 2018.2 preview and got that up and running. Good stuff and I gave myself a pad on the shoulder at that point.
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'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!
Well, now we got noPWS container with IRIS, and how to connect to it, simply, without any durable sys or files, using normal peoples way like Environment variables?
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 ? )
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.
Does anyone have experience with installing the Arbiter Container using Podman instead of Docker in a Red Hat environment? I was able to pull down the docker image, but unsure what are the next steps as I am confused on how to start the container using Podman and ensure the parameters are set appropriately? Does anyone have the steps that I should take? Should I go through the WRC? Does the WRC have experience using Podman?
Or should I just install the ISC Agent instead of using the Container?
Has anyone seen this before? I'm new/bad at Docker and not even sure how to debug.
$ sudo docker logs <container> [INFO] Starting InterSystems IRIS instance IRIS... [INFO] Unable to read the startup.last file to identify the location of the write image journal file (IRIS.WIJ) that was last in use by this instance. Please fix the permissions of the startup.last file.
I wanted to write it as a comment toarticle of @Evgeny Shvarov . But it happens to be so long, so, decided to post it separately.
I would like to add a bit of clarification about how docker uses disk space and how to clean it. I use macOS, so, everything below, is mostly for macOS, but docker commands suit any platform.
The title says it all. I’m building an IRIS image with docker-compose using a separate Dockerfile. Pretty straightforward procedure: I import a Installer script inside the container containing a Installer Manifest I defined. Within the manifest, I create a namespace with code and data databases in separate locations. My intention is to keep the code database inside the container, so whenever I build the container, the imported code is replaced. The data, however, should be persistent.
https://www.youtube.com/embed/lgDCkGvjL8I [This is an embedded link, but you cannot view embedded content directly on the site because you have declined the cookies necessary to access it. To view embedded content, you would need to accept all cookies in your Cookies Settings]
By replies
