Update dir ownership for additionalVolumeMounts in initContainers
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 191
- Forks
- 98
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 6
Description
As of now, initContainers only update following mountpath during init step, but not for additionalVolumeMounts.
Background: I want to add an NFS for snapshot dir, and I add following configs,
`additionalVolumes:
- name: efs-mount
nfs:
path: /
server: fs-xxxx.efs.eu-central-1.amazonaws.com
additionalVolumeMounts:
- name: efs-mount
mountPath: "/qdrant/efs-snapshots"`
In this case, qdrant will fail to start due to permission issue.
Panic occurred in file lib/storage/src/content_manager/toc/mod.rs at line 126: Can't create a directory for snapshot of xxx: Permission denied (os error 13)
I tried to set additionalVolumeMounts to /qdrant/snapshots, but we already have a default item for this, so there will be 2 volumes mounting on same path, and cause failure
Contributor guide
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 by tracing the Helm templates that render initContainers, additionalVolumes, and additionalVolumeMounts, then compare them with the ownership behavior described in lib/storage/src/content_manager/toc/mod.rs. Reproduce the NFS configuration from the issue and verify that the snapshot directory can be created without a permission error and without duplicate mounts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100