Answers to: Docker, prevent container being stopped after an exception

Answer by Alex Suter

Alex Suter — Thu, 16 May 2019 10:41:13 -0400

It's better to not start the engine at all if a problem like this occur, this can lead to very unexpected behaviors. If the engine can not access the ivy.yaml a lot of problems can occur.

And in fact everything is said when you got the message 'Permission denied'. E.g. you can't start an apache http server if it can not access its configuration files.

In your case now, please check the file permissions (chown/chmod) of your ivy.yaml. I suppose that you must set the user and group to ivy:ivy.

Comment by John Moser on John Moser's question

John Moser — Thu, 16 May 2019 08:32:35 -0400

The problem is, you can't connect to the container anymore if something like this ... Caused by: java.io.FileNotFoundException: /etc/axonivy-engine-7x/ivy.yaml (Permission denied) ... happens. It would be nice to keep the container up and running in order to connect and investigate, what went wrong.

Comment by Alex Suter on John Moser's question

Alex Suter — Thu, 16 May 2019 02:35:42 -0400

What do you mean with a fatal exception in ivy. A fatal exception is something like OutOfMemory and there is no way out. This is not specific to ivy.