fix(lightspeed): fix rag-content folder ownership in init container#460
Conversation
…tebooks in init … (redhat-developer#449) * On EKS/AKS, the RAG init container populates /rag-content/ but never creates the notebooks subdirectory. At runtime, llama-stack tries to write /rag-content/vector_db/notebooks/faiss_store.db and fails with PermissionError because it cannot create the directory on a volume it doesn't own. OCP avoids this via fsGroup/supplemental group defaults. The fix pre-creates the directory and widens permissions before the sidecar starts, matching the fix the operator already applies via chmod -R 777 for the rest of vector_db. Signed-off-by: Lucas <lyoon@redhat.com> * Apply suggestions from code review Co-authored-by: Armel Soro <armel@rm3l.org> --------- Signed-off-by: Lucas <lyoon@redhat.com> Co-authored-by: Armel Soro <armel@rm3l.org>
d097331 to
ed2a1af
Compare
|
PR Summary by QodoFix Lightspeed RAG init container ownership/permissions for /rag-content notebooks
AI Description
Diagram
High-Level Assessment
Files changed (5)
|
837bccc
into
redhat-developer:main
…ack to 0.5.2 Use --no-preserve=mode,ownership when copying RAG data so the sidecar (UID 1001) can access files written by the init container (UID 65532). Pre-create the notebooks subdirectory and chmod the copied data to prevent PermissionError on vanilla Kubernetes. Also bump lightspeed-stack sidecar from 0.5.1 to 0.5.2. Refs: - redhat-developer#460 - redhat-developer#461 Assisted-by: Claude




manual cherry-pick of #449