Skip to content
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

Closed
quulah opened this issue Sep 5, 2022 · 5 comments
Closed

Self-hosted runners with rootless Docker broken after 2.296.1 #2103

quulah opened this issue Sep 5, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@quulah
Copy link

quulah commented Sep 5, 2022

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?

unable to resolve docker endpoint: context "rootless" does not exist

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 setting DOCKER_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

@quulah quulah added the bug Something isn't working label Sep 5, 2022
@quulah
Copy link
Author

quulah commented Sep 5, 2022

There's #827 which is most likely related, but until the recent update to the runner this has actually worked for us.

@quulah
Copy link
Author

quulah commented Sep 5, 2022

Pinning to 2.296.0 seems to have helped and our builds aren't failing anymore.

While I was at it, I set the DOCKER_HOST to point at the correct socket in the runner's .env. Not quite sure if that has an effect on this or not, but doesn't seem to hurt either.

@thboop
Copy link
Collaborator

thboop commented Sep 6, 2022

Thanks for the report, we are working on a fix!

@ghost
Copy link

ghost commented Sep 13, 2022

Hello everyone! Is this issue related to this community feedback or should I open/add it to a different one?

@quulah
Copy link
Author

quulah commented Sep 14, 2022

@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.

@quulah quulah closed this as completed Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants