Container restart results in error due to file permission errors

[tsilikasg]

Hello all,

We are testing the MUKIB MISP container in Azure container instances however, whenever there is a container restart, MISP will NOT come back automatically since the following files (config.php,database.php,email.php) in the Config directory are now read-only after a succesfull start. I was wondering how other users have resolved this issue and what is the proper way to handle this situation.

Please note that the configuration directory (/var/www/MISP/app/Config/) is a mounted volume in an external storage account.

Best regards,
George.

[ondj]

Hello, why you mount /var/www/MISP/app/Config/ as volume? This should not be necessary, as files in this directory are generated when container starts from environment variables.

[tsilikasg]

Hi ondj,

We want to have a persistant site that will survive a container restart and even a new instance deployment. Is there an other way to do so?

[ondj]

As I said, all config files are generated when you restart container. What do you need to modify?