mirror of
https://gitea.com/gitea/act_runner.git
synced 2025-01-30 13:31:20 +00:00
8dfb805c62
With the changes made two months ago for the Dockerfile /opt/act/run.sh no longer exists in the docker container, this caused this example to fail, updating the example so that it correctly references run.sh now located in /usr/local/bin I have used this to deploy on my own cluster and it is now working swimmingly Reviewed-on: https://gitea.com/gitea/act_runner/pulls/633 Reviewed-by: Zettat123 <zettat123@noreply.gitea.com> Reviewed-by: techknowlogick <techknowlogick@noreply.gitea.com> Co-authored-by: armistace <armistace@noreply.gitea.com> Co-committed-by: armistace <armistace@noreply.gitea.com>
Kubernetes Docker in Docker Deployment with act_runner
NOTE: Docker in Docker (dind) requires elevated privileges on Kubernetes. The current way to achieve this is to set the pod SecurityContext
to privileged
. Keep in mind that this is a potential security issue that has the potential for a malicious application to break out of the container context.
Files in this directory:
-
dind-docker.yaml
How to create a Deployment and Persistent Volume for Kubernetes to act as a runner. The Docker credentials are re-generated each time the pod connects and does not need to be persisted. -
rootless-docker.yaml
How to create a rootless Deployment and Persistent Volume for Kubernetes to act as a runner. The Docker credentials are re-generated each time the pod connects and does not need to be persisted.