Permission issues on storage-manager instances
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 3
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
The storagemanager has a hardcoded image that is tracking the latest updates, resulting in permission issues since filebrowser updated their docker image to use a custom user, in this commit.
This line needs to be changed, preferably to a value that is read from the config.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at service/v2/sms/resources/k8s_generator.go line 93 and inspect how the storage-manager image is selected and how configuration is supplied. Review the referenced filebrowser image change and confirm the generated resource no longer causes permission issues. Done means the image value is no longer hardcoded and storage-manager instances retain usable permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100