starred/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2026-02-24 19:08:59 +03:00
Code Issues 396 Packages Projects Releases 16 Wiki Activity

[Bug]: Helm Chart Volume Mount Root Permissions #611

New Issue
Open
opened 2026-02-04 20:33:31 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-04 20:33:31 +03:00
Owner
Copy Link

Originally created by @B1ue-W01f on GitHub (Nov 22, 2024).

Where is the problem occurring?

I encountered the problem while interacting with the server (Backend)

What browsers are you seeing the problem on?

Chrome

Current behaviour

Current helm chart results in the 'project-background-images' and 'user-avatars' directories being mounted as root, this prevents uploads from working with a permission denied log message.

Desired behaviour

Default values.yaml file should initiate a working application.

I believe - though could be wrong - the below entries should be made in the values.yaml file, these can be further customised by a user if required but would prevent standing up a none working app.

podSecurityContext:
  fsGroup: 1000

Steps to reproduce

Follow guidance here:

https://docs.planka.cloud/docs/installation/kubernetes/helm_chart

Leave values.yaml as default.

Other information

Id be happy to make a pull request if the proposed solution appears correct to others.

Originally created by @B1ue-W01f on GitHub (Nov 22, 2024). ### Where is the problem occurring? I encountered the problem while interacting with the server (Backend) ### What browsers are you seeing the problem on? Chrome ### Current behaviour Current helm chart results in the 'project-background-images' and 'user-avatars' directories being mounted as root, this prevents uploads from working with a permission denied log message. ### Desired behaviour Default values.yaml file should initiate a working application. I believe - though could be wrong - the below entries should be made in the values.yaml file, these can be further customised by a user if required but would prevent standing up a none working app. ``` podSecurityContext: fsGroup: 1000 ``` ### Steps to reproduce Follow guidance here: https://docs.planka.cloud/docs/installation/kubernetes/helm_chart Leave values.yaml as default. ### Other information Id be happy to make a pull request if the proposed solution appears correct to others.
OVERLORD added the help wanted label 2026-02-04 20:33:31 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
bug
documentation
documentation
duplicate
enhancement
good first issue
help wanted
pull-request
Mirrored from GitHub Pull Request
 question
wontfix
No Label help wanted
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/planka#611
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?