Mounting NFS volume from self-hosted runner #60526
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Question
Body
I am running self-hosted runners in EKS (kubernetes), using ARC and configured with horizontal runner autoscaler.
We have a use case where a user needs to mount an AWS EFS (NFS) volume in their workflow. When they try, it is getting an error b'mount.nfs4: Operation not permitted'. On a test pod I created (just running CentOS), I saw the same error on a mount attempt, but was able to resolve by setting securityContext: privileged: true on the pod deployment.
I have been reading through documentation, but can not understand where I would make the edit to a config file to either set the securityContext to privileged: true for the runner pods being created, or otherwise update the security permissions to just allow the mount command to be run.
I did try adding it to my RunnerDeployment, but it gets errors trying to validate (does not like 'privileged' here)
Beta Was this translation helpful? Give feedback.
All reactions