You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

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

If you find it hard to have your local IMAS installation, it might be you 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 slightly limited functionality, a Docker based IMAS release if the way for you to go.

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 server and UDA client based on IMAS inside Docker, we have released SimDB installations based on IMAS inside Docker, finally, we provide CI/CD based tests at https://gitlab.eufus.psnc.pl that are based on IMAS inside Docker. And all of that thanks to Docker images with IMAS inside.

You can benefit from this solution, and it is extremely simple. All you have to do is to create your Dockerfile such way it is based on ours

Create your own Docker image based on IMAS

> 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
...
...


That's it. You have a Docker image with IMAS inside. Feel free to add anything you like on top of it.

  • No labels

The scientific work is published for the realization of the international project co-financed by Polish Ministry of Science and Higher Education in 2019 from financial resources of the program entitled "PMW"; Agreement No. 5040/H2020/Euratom/2019/2.

This work has been carried out within the framework of the EUROfusion Consortium and has received funding from the Euratom research and training programme 2014–2020 under grant agreement No 633053.

This work has been carried out within the framework of the EUROfusion Consortium, funded by the European Union via the Euratom Research and Training Programme (Grant Agreement No. 101052200-EUROfusion). Views and opinions expressed are however those of the author(s) only and do not necessarily reflect those of the European Union or the European Commission. Neither the European Union nor the European Commission can be held responsible for them.

The project activities are co-financed by Polish Ministry of Science and Higher Education from financial resources of the programme entitled "PMW" in 2023, 2024.

The views and opinions expressed herein do not necessarily reflect those of the European Commission or ITER