Dear Ivy Team

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.

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

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.

Or do I miss something ?

Best regards John

asked 15.07 at 12:20

John%20Moser's gravatar image

John Moser
362414
accept rate: 0%

Hi John What version of Ivy and the sample are you using? In the newest 7.4 Dev version we addressed exactly this problem: - XIVY-3082: Support ivyProjects in application directory located in project specific Docker Image

Have a look at this sample: https://github.com/ivy-samples/docker-samples/tree/master/ivy-deploy-app How does your docker-compose.yml and Dockerfile look like? How do you deploy your app?

(24.07 at 07:45) Andreas Rusch Andreas%20Rusch's gravatar image

@Andreas : I've went through all the documentation. The point is if Ivy IAR (same version) installation is reentrant or not and if not, why ?

(26.07 at 04:12) John Moser John%20Moser's gravatar image

How do you run docker-compose? What are your build steps? I can't replicate your issue.

To get a new DB from scratch you would need to run 'docker-compose down'. Otherwise you are reusing your DB container.

What do you mean with 're-entrant'? If the same version of a IAR can be deployed multiple times? Yes, it can.

If you are NOT using the newest dev version: Are you specifying your application folder outside the container? With versions 7.2.1 and 7.3.1 you run into problems if you try to redeploy a project where the app folder didn't include the old project (and files).

(29.07 at 09:05) Andreas Rusch Andreas%20Rusch's gravatar image

Hello @John Moser

The systemdb in our docker-compose example are only created from scratch at the first docker-compose up. After that it's always the same container when starting and stopping. If you remove this container with docker-compose down, there will be a new container with the next docker-compose up. You can map the persistent data of the database container to a volume to never lose the system database even after docker-compose down.

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.

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.

If you want to deploy a new iar you will need a new image.

link

answered 07.08 at 03:55

Alex%20Suter's gravatar image

Alex Suter ♦♦
2.2k91936
accept rate: 83%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "Title")
  • image?![alt text](/path/img.jpg "Title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×8

Asked: 15.07 at 12:20

Seen: 91 times

Last updated: 07.08 at 03:55