# Plugin installation fail

**URL:** <https://forum.mattermost.com/t/plugin-installation-fail/15672>\
**Category:** Troubleshooting\
**Created:** [April 14, 2023, 10:01am UTC](https://forum.mattermost.com/t/plugin-installation-fail/15672 "2023-04-14T10:01:09Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![360](https://avatars.discourse-cdn.com/v4/letter/3/51bf81/32.png) [@360](https://forum.mattermost.com/u/360)\
**Post date:** [April 14, 2023, 10:01am UTC](https://forum.mattermost.com/t/plugin-installation-fail/15672/1 "2023-04-14T10:01:09Z")

</div>

**Summary**  
Hello I use mattermost 7.7.0 team edition deployed with this char helm [mattermost-helm/charts/mattermost-enterprise-edition at master · mattermost/mattermost-helm · GitHub](https://github.com/mattermost/mattermost-helm/tree/master/charts/mattermost-enterprise-edition)

The plugin installation fail

**Steps to reproduce**  
Activate plugins

**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 ?

---

<div class="post-metadata">

**Author:** ![agriesser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/agriesser/32/5644_2.png) [@agriesser](https://forum.mattermost.com/u/agriesser)\
**Post date:** [April 17, 2023, 4:11am UTC](https://forum.mattermost.com/t/plugin-installation-fail/15672/2 "2023-04-17T04:11:19Z")

</div>

Hi @360 ,

I think this is related to your previous topic, so I’m linking them here:

> [@Plugin activation problem](https://forum.mattermost.com/t/plugin-activation-problem/14865):
>
> Summary Can’t activate plugins Steps to reproduce Activate plugins Expected behavior Plugins are available Observed behavior Hello, I use mattermost 7.7.0 team edition deployed via the chart helm [mattermost-helm/charts/mattermost-team-edition at master · mattermost/mattermost-helm · GitHub](https://github.com/mattermost/mattermost-helm/tree/master/charts/mattermost-team-edition) When I want to activate plugins I saw that pluging pre included (like playbooks) are not available after the activation. I checked the logs and there are logs after my activation. {"timestamp":"2023-…

I’m unable to help you with this issue, because I do not use K8S, but I’ll see if I can find someone who’s able to help.

---

<div class="post-metadata">

**Author:** ![360](https://avatars.discourse-cdn.com/v4/letter/3/51bf81/32.png) [@360](https://forum.mattermost.com/u/360)\
**Post date:** [May 16, 2023, 1:03pm UTC](https://forum.mattermost.com/t/plugin-installation-fail/15672/3 "2023-05-16T13:03:18Z")

</div>

Hello @agriesser

Any news ? I still encouter this problem issue in 7.9.3 and plugins are important functionalities for my company

---

<div class="post-metadata">

**Author:** ![agriesser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/agriesser/32/5644_2.png) [@agriesser](https://forum.mattermost.com/u/agriesser)\
**Post date:** [May 20, 2023, 9:42am UTC](https://forum.mattermost.com/t/plugin-installation-fail/15672/4 "2023-05-20T09:42:55Z")

</div>

Hi @360 ,

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:

> [@Mattermost v7.9.1 team-edition helm deployment issues](https://forum.mattermost.com/t/mattermost-v7-9-1-team-edition-helm-deployment-issues/15434/18):
>
> I found a workaround. Add this to you helm values: extraInitContainers: - command: - sh - '-c' - chown -R 2000:2000 /client/plugins image: busybox name: changeowner volumeMounts: - mountPath: /client/plugins name: mattermost-plugins This runs a init container which changes the owner of the plugins folder.

---

<div class="post-metadata">

**Author:** ![360](https://avatars.discourse-cdn.com/v4/letter/3/51bf81/32.png) [@360](https://forum.mattermost.com/u/360)\
**Post date:** [May 24, 2023, 8:41am UTC](https://forum.mattermost.com/t/plugin-installation-fail/15672/5 "2023-05-24T08:41:22Z")

</div>

Hello,

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”

---

<div class="post-metadata">

**Author:** ![agriesser](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/agriesser/32/5644_2.png) [@agriesser](https://forum.mattermost.com/u/agriesser)\
**Post date:** [May 24, 2023, 9:05am UTC](https://forum.mattermost.com/t/plugin-installation-fail/15672/6 "2023-05-24T09:05:31Z")

</div>

Could you maybe ask in the other thread? I’ve no test environment for that and cannot help with that issue, sorry.
