Expected behavior
plugin are installed and available in the app
Observed behavior
plugin installation failed. There is an example of plugin installation faillure
{"timestamp":"2023-04-14 07:09:37.199 Z","level":"error","msg":"Failed to install prepackaged plugin","caller":"app/plugin.go:967","path":"/mattermost/prepackaged_plugins/mattermost-plugin-nps-v1.3.1-linux-amd64.tar.gz","error":"Failed to install extracted prepackaged plugin /mattermost/prepackaged_plugins/mattermost-plugin-nps-v1.3.1-linux-amd64.tar.gz: installExtractedPlugin: Unable to move plugin from temporary directory to final destination. Another plugin may be using the same directory name., mkdir plugins/com.mattermost.nps: permission denied"}
I think this is “normal” because the chart make the volume “plugin” be mounted on the container in the mattermost/client/plugins and the plugin try to be installed in the mattermost/plugin folder where no volume is mounted. Did I miss something ?
as I said, I’m not using Kubernetes here, so I don’t have a solution or workaround, but please have a look here, this user posted a workaround that might also help you:
Thank you for your answer. It looks like other users has exactly the same right problem than me that cause plugin installation faillure. I tested the workaround posted by this user but my init container has no right to change the right on the folder /client/plugins “operation not permitted”