<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Answers to: Docker, Rerun image with IAR installation</title><link>https://answers.axonivy.com/questions/3891/docker-rerun-image-with-iar-installation</link><description>&lt;p&gt;Dear Ivy Team&lt;/p&gt;
&lt;p&gt;In your example setup, the ivysystemdb exists as an image and is therefore created from scratch every time docker-compose is run. That means you can run the same image as many times as you want.&lt;/p&gt;
&lt;p&gt;If we do that in our Dev environment, we are running into the versioning problem (I think), which prevents to rerun of the same image multiple times (Error : The process model version '1' of process model 'luz_web' of application 'luz' is currently unavailable because of maintenance.) &lt;/p&gt;
&lt;p&gt;Since our image does the installation as well, it can't be "used" more then one time, which means for each restart we would need a new build of a new version of our app.&lt;/p&gt;
&lt;p&gt;Or do I miss something ?&lt;/p&gt;
&lt;p&gt;Best regards
John&lt;/p&gt;</description><atom:link href="https://answers.axonivy.com/questions/3891/docker-rerun-image-with-iar-installation" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 07 Aug 2019 03:55:06 -0400</lastBuildDate><item><title>Answer by Alex Suter</title><link>https://answers.axonivy.com/questions/3891/docker-rerun-image-with-iar-installation/3909</link><description>&lt;p&gt;Hello &lt;a href="https://answers.axonivy.com/users/1123/john-moser"&gt;&lt;a href="https://answers.axonivy.com/users/1123/john-moser"&gt;@John Moser&lt;/a&gt;&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;The systemdb in our docker-compose example are only created from scratch at the first &lt;code&gt;docker-compose up&lt;/code&gt;. After that it's always the same container when starting and stopping. If you remove this container with &lt;code&gt;docker-compose down&lt;/code&gt;, there will be a new container with the next &lt;code&gt;docker-compose up&lt;/code&gt;. You can map the persistent data of the database container to a volume to never lose the system database even after &lt;code&gt;docker-compose down&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;If there is always a new systemdb from scratch, you will never run in versioning problems. Prior to 7.4 you run in version problems when you have the same systemdb for new iar deployment (new image, which does not contain the old iar), but this has been fixed with 7.4.&lt;/p&gt;
&lt;p&gt;You can restart your axonivy container as many times as you want - you can also create new containers from the same image as many times as you want.&lt;/p&gt;
&lt;p&gt;If you want to deploy a new iar you will need a new image.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Alex Suter</dc:creator><pubDate>Wed, 07 Aug 2019 03:55:06 -0400</pubDate><guid>https://answers.axonivy.com/questions/3891/docker-rerun-image-with-iar-installation/3909</guid></item></channel></rss>