Github actions self-hosted-runners using AWS EKS Fargate. #138162
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 facing issues regarding self-hosted-runners in Github actions using AWS EKS Fargate.
I used this file to create runner in github.
`apiVersion: actions.summerwind.dev/v1alpha1
kind: RunnerDeployment
metadata:
name: k8s-action-runner
namespace: fargate-runner
spec:
replicas: 1
template:
spec:
repository: karthikreddy456/react-workflow-gh-actions
dockerEnabled: false
labels:
- "fargate_runner"
But by default it creates runner with Linux as base image. but i want to use my custom docker image to deploy the runner. How can i do that.
I got error
Events:
Type Reason Age From Message
Warning FailedScheduling 110s fargate-scheduler Pod not supported on Fargate: invalid SecurityContext fields: Privileged
so i put the line dockerEnabled: false in the manifest file. The runner is working fine but when i use the runner some jobs steps like npm install is not working in fargate but when i run the same workflow file using Nodegroups it is working fine.
Is there a way to use custom Docker image for the above?
`
Beta Was this translation helpful? Give feedback.
All reactions