7 Commits

Include renames

Author	SHA1	Message	Date
Daniel HobleyandGitHub	90ea691e72	feat: allow for modifying var-run mount maximum size limit (#2624)	2023-05-27 11:47:23 +09:00
Yusuke KuokaandGitHub	94c089c407	Revert docker.sock path to /var/run/docker.sock (#2536) ... Starting ARC v0.27.2, we've changed the `docker.sock` path from `/var/run/docker.sock` to `/var/run/docker/docker.sock`. That resulted in breaking some container-based actions due to the hard-coded `docker.sock` path in various places. Even `actions/runner` seem to use `/var/run/docker.sock` for building container-based actions and for service containers? Anyway, this fixes that by moving the sock file back to the previous location. Once this gets merged, users stuck at ARC v0.27.1, previously upgraded to 0.27.2 or 0.27.3 and reverted back to v0.27.1 due to #2519, should be able to upgrade to the upcoming v0.27.4. Resolves #2519 Resolves #2538	2023-04-27 13:06:35 +09:00
Yusuke KuokaandGitHub	3e0bc3f7be	Fix docker.sock permission error for non-dind Ubuntu 20.04 runners since v0.27.2 (#2499) ... #2490 has been happening since v0.27.2 for non-dind runners based on Ubuntu 20.04 runner images. It does not affect Ubuntu 22.04 non-dind runners(i.e. runners with dockerd sidecars) and Ubuntu 20.04/22.04 dind runners(i.e. runners without dockerd sidecars). However, presuming many folks are still using Ubuntu 20.04 runners and non-dind runners, we should fix it. This change tries to fix it by defaulting to the docker group id 1001 used by Ubuntu 20.04 runners, and use gid 121 for Ubuntu 22.04 runners. We use the image tag to see which Ubuntu version the runner is based on. The algorithm is so simple- we assume it's Ubuntu-22.04-based if the image tag contains "22.04". This might be a breaking change for folks who have already upgraded to Ubuntu 22.04 runners using their own custom runner images. Note again; we rely on the image tag to detect Ubuntu 22.04 runner images and use the proper docker gid- Folks using our official Ubuntu 22.04 runner images are not affected. It is a breaking change anyway, so I have added a remedy- ARC got a new flag, `--docker-gid`, which defaults to `1001` but can be set to `121` or whatever gid the operator/admin likes. This can be set to `--docker-gid=121`, for example, if you are using your own custom runner image based on Ubuntu 22.04 and the image tag does not contain "22.04". Fixes #2490	2023-04-17 21:30:41 +09:00
3 people	878c9b8b49	runner: Use Docker socket via shared emptyDir instead of TCP/mTLS (#2324) ... Co-authored-by: Yusuke Kuoka <ykuoka@gmail.com>	2023-03-28 11:29:16 +09:00
Tingluo HuangandGitHub	044c8ad4d5	Include actions-runner-controller in runner's User-Agent for better telemetry in Actions service. (#2155)	2023-01-15 09:35:56 +09:00
3 people	eaa451df32	Update controller package names to match the owning API group name (#2150) ... * Update controller package names to match the owning API group name * feedback. Co-authored-by: Bassem Dghaidi <568794+Link-@users.noreply.github.com>	2023-01-13 08:24:11 +09:00
3 people	aa6dab5a9a	Changes to folder structure to allow multigroups and changed go mod name (#2105) ... * Changed folder structure to allow multi group registration * included actions.github.com directory for resources and controllers * updated go module to actions/actions-runner-controller * publish arc packages under actions-runner-controller * Update charts/actions-runner-controller/docs/UPGRADING.md Co-authored-by: Yusuke Kuoka <ykuoka@gmail.com>	2022-12-28 09:38:34 +09:00