Open rdvansloten opened 4 months ago
Hello! Thank you for filing an issue.
The maintainers will triage your issue shortly.
In the meantime, please take a look at the troubleshooting guide for bug reports.
If this is a feature request, please review our contribution guidelines.
I'm running into the same issue using rootless images.
Same boat here, on 0.9.2. It's odd because this is only occurring on one of 3 runnersets, all using the same helm chart and cluster
Submitted a fix (#3740) for this.
I'm encountering this when trying to use values.yaml to specify my runner image:
template:
spec:
containers:
- name: runner
image: private-repo.com/actions-runner:latest
command: ["/home/runner/run.sh"]
which is built using Dockerfile:
FROM summerwind/actions-runner:latest
USER root
RUN echo 'APT::Install-Suggests "0";' >> /etc/apt/apt.conf.d/00-docker
RUN echo 'APT::Install-Recommends "0";' >> /etc/apt/apt.conf.d/00-docker
RUN <<EOF
. /etc/os-release
wget -q https://packages.microsoft.com/config/ubuntu/$VERSION_ID/packages-microsoft-prod.deb
dpkg -i packages-microsoft-prod.deb
rm packages-microsoft-prod.deb
DEBIAN_FRONTEND=noninteractive
apt-get update
apt-get install -y -qq powershell
EOF
USER runner
problem went away when using ghcr.io/actions/actions-runner:latest
as base image instead of summerwind/actions-runner:latest
Checks
Controller Version
0.9.3
Deployment Method
Helm
Checks
To Reproduce
Describe the bug
Expected my init-dind-externals to work.
Describe the expected behavior
init-dind-externals should start, so that my runner can.
Additional Context
Runner Pod Logs