-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Newest actions-runner-dind container failing to start #2143
Comments
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. |
@apenney what image are you using? summerwind/actions-runner, dind or dind+rootless? |
actions-runner-dind - I just did some testing (and added logs) - actions-runner-dind:ubuntu-20.04 works fine, actions-runner-dind:ubuntu-22.04 does not - so it's definitely isolated to 22.04 and not anything else. |
|
Looks to be related to the upstream Debian change to nftables from iptables: https://wiki.debian.org/iptables. There's a workaround in there that might be worth trying and reporting back:
|
Thanks so much.@apenney I had a same problem and solved it |
I had the same error and needed to revert back to previous image and pipelines started to work again. We will wait for a fix. Working image: |
I wanted to report the same error, i have temporarily solved by using 20.04 as well |
Had the same issue with the latest image, and switched to the previous tag |
I've tested the following images in our GKE 1.25 environment running ARC 0.26.0 via helm chart version: 0.21.0. ghcr.io/actions/actions-runner-controller/actions-runner-dind-rootless:v2.299.1-ubuntu-22.04-aa6dab5 ✅ The only way I can get those similar errors to occur is to have |
The actions-runner-controller/releases#1 has addressed this problem and we're re-releasing the runner images with the appropriate tags. Apologies for this! |
Runner images have been tagged appropriately, which should resolve these problems. I'm going to keep this issue open pending a confirmation that you're all good 👍 |
all solved for me, thanks |
I fixed the issue with dind on ubuntu 22.04 by adding to my custom image this line
then dind started working correctly. |
Checks
Controller Version
2.300.2
Helm Chart Version
v0.21.0
CertManager Version
1.9.1
Deployment Method
Helm
cert-manager installation
.
Checks
Resource Definitions
.
To Reproduce
Describe the bug
We were previously pulling :latest and upon the latest release (3 hours ago) we realized all our runners were failing with a looping:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
We ended up fixing by just pinning back to v2.299.1-ubuntu-20.04-aa6dab5 which allowed us to start things back up. We're going to do some troubleshooting to figure out what happened, but I wanted to get a placeholder issue in for anyone else who runs into this (assuming it's not hyper specific to our setup)
Describe the expected behavior
.
Whole Controller Logs
Whole Runner Pod Logs
Additional Context
No response
The text was updated successfully, but these errors were encountered: