# Mattermost v7.9.1 team-edition helm deployment issues

**URL:** <https://forum.mattermost.com/t/mattermost-v7-9-1-team-edition-helm-deployment-issues/15434>\
**Category:** Troubleshooting\
**Created:** [March 19, 2023, 3:03pm UTC](https://forum.mattermost.com/t/mattermost-v7-9-1-team-edition-helm-deployment-issues/15434 "2023-03-19T15:03:25Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![michaelkoelle](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mattermost.com/michaelkoelle/32/6809_2.png) [@michaelkoelle](https://forum.mattermost.com/u/michaelkoelle)\
**Post date:** [May 19, 2023, 2:24pm UTC](https://forum.mattermost.com/t/mattermost-v7-9-1-team-edition-helm-deployment-issues/15434/18 "2023-05-19T14:24:37Z")

</div>

I found a workaround. Add this to you helm values:

```auto
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.

---

_[View the full topic](https://forum.mattermost.com/t/mattermost-v7-9-1-team-edition-helm-deployment-issues/15434)._