-
Notifications
You must be signed in to change notification settings - Fork 976
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
Self-hosted runners with rootless Docker broken after 2.296.1 #2103
Comments
There's #827 which is most likely related, but until the recent update to the runner this has actually worked for us. |
Pinning to 2.296.0 seems to have helped and our builds aren't failing anymore. While I was at it, I set the |
Thanks for the report, we are working on a fix! |
Hello everyone! Is this issue related to this community feedback or should I open/add it to a different one? |
@hjokunbus I'm unsure whether your issue is related or not, but I suggest opening a new one in any case. Looks a bit different. And 2.296.2 seems to have fixed our problem, so I'll close this. |
Describe the bug
We run self-hosted runners with rootless Docker set up.
After 2.296.1 hit, jobs with
container:
that worked previously, have now started failing in early stages.Specifically in "Initializing containers" "Starting job container".
To Reproduce
Expected behavior
Well, it should work. :)
Runner Version and Platform
Version of your runner?
2.296.1
OS of the machine running the runner? OSX/Windows/Linux/...
Ubuntu 20.04.4 LTS
What's not working?
My best guess is that it is trying to talk to the
/var/run/docker.sock
instead of the rootless socket of the runner user, but settingDOCKER_HOST
in the jobs does not help as it previously has for some cases such as building a container image within.Job Log Output
Runner and Worker's Diagnostic Logs
The text was updated successfully, but these errors were encountered: