actions / actions/actions-runner-controller
docker inside docker for non-privileged environments
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 6.5k
- Forks
- 1.5k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 27
Description
What would you like added?
A clear and concise description of what you want to happen.
we can run the pods an non-root in our environments , since docker run needs privileged pods , we are not able to execute docker run inside the runners .
is there any other solution to make docker run for non-privileged setup
Why is this needed?
we can run the pods an non-root in our environments , since docker run needs privileged pods , we are not able to execute docker run inside the runners .
is there any other solution to make docker run for non-privileged setup
Additional context
Docker run support for non-privileged environments
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 reviewing how the controller configures runner pods and handles Docker-in-Docker or privileged execution. Determine whether a supported non-privileged Docker solution fits the project, and document or implement the approach only if its security and Kubernetes requirements are clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100