[bitnami/matomo] config/config.ini.php not writeable unable to install plugins

[fabianboerner]

Name and Version

bitnami/matomo 8.0.5

What architecture are you using?

amd64

What steps will reproduce the bug?

default setup for matomo helm chart.

1. Go to market place
2. install plugin
3. activate plugin
4. message config/config.ini.php not writeable changes are not stored.

Are you using any custom parameters or values?

i have tried:

customPostInitScripts: custom-post-init.sh: |

!/bin/bash

  chmod 777 /bitnami/matomo/config/config.ini.php

All other settings are for password and smtp.

What is the expected behavior?

Plugin is installed.

What do you see instead?

Additional information

No response

[fabianboerner]

When i deploy everything it works the moment i changed it the first time and it seems something redeploys it stops working again.

[dgomezleon]

Hi @fabianboerner ,

I couldn't reproduce the issue on GKE with the default values. I installed and activate Queued tracking.

Did you try a different plugin?

You could also try changing the containerSecurityContext:

containerSecurityContext:
  readOnlyRootFilesystem: false
  runAsGroup: 0

I hope it helps

[fabianboerner]

It seems it was the storage class from digital ocean when first installed it was readable.

After i deployed changes the error occured and the only thing that was not changed was the pvc on the digital ocean storage class.

I implemented an nfs controller with a new storage class and that has solved the problem.

https://www.digitalocean.com/community/tutorials/how-to-set-up-readwritemany-rwx-persistent-volumes-with-nfs-on-digitalocean-kubernetes-de

[dgomezleon]

Thanks for sharing your solution here.

[github-actions[bot]]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions[bot]]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.