Why should I use Docker containers with IMAS in a first place

If you find it hard to have your local IMAS installation, think of the possible sources of this issue. It might be you will find yourself in one of these situations:

• you have a computing cluster but you don't have root permissions to install new software,
• you need just bare bones IMAS installation, with basic components, but you don't have a computing machine and manpower to install it,
• you don't have to time to perform regular upgrades of your IMAS installation,
• you want to utilise Cloud resources.

Indeed, having a local IMAS installation may be a challenge. However, there is a solution, in case you need your private IMAS release with limited functionality - Docker based IMAS release.

We have successfully used this approach across various projects and were able to deliver solutions from embedding single physical code to complex, micro-services based, server solutions. We were able to provide UDA servers and clients, SimDB installations, CI/CD based tests, and all of that thanks to Docker based IMAS.

You can also benefit from it and it's extremely simple. All you have to do is to create your Docker based on our solution

{code}
> cat ~/mycontainer/Dockerfile

FROM gitlab.eufus.psnc.pl:5050/containerization/imas/imas-installer/al-iwrap:DD-4.0.0_AL-5.4.1_IWRAP-0.10.0-UDA-2.8.1-UDA-PLUGIN-1.5.0
...
...
{code}