Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Runner does not start anymore #219

Closed
vmk-dev opened this issue Jun 16, 2022 · 4 comments
Closed

Runner does not start anymore #219

vmk-dev opened this issue Jun 16, 2022 · 4 comments

Comments

@vmk-dev
Copy link

vmk-dev commented Jun 16, 2022

When starting the runner with the latest image tag I get this error:

Runner reusage is disabled
Obtaining the token of the runner
curl: (6) getaddrinfo() thread failed to start
Disable auto update option is enabled
Configuring
Failed to create CoreCLR, HRESULT: 0x80070008
Failed to create CoreCLR, HRESULT: 0x80070008

Any ideas?

@myoung34
Copy link
Owner

This is a dupe of #216
Im going to roll back latest to focal due to the widespread nature of jammy

@myoung34
Copy link
Owner

Testing with 4064635

cc @Ru13en for a #211 regression. Jammy will be available as a named tag but not latest

@vmk-dev
Copy link
Author

vmk-dev commented Jun 17, 2022

@myoung34 thank you for the quick response. Just pulled the latest tag of your rolled back image and now it works like a charm again!

@Ru13en
Copy link
Contributor

Ru13en commented Jun 18, 2022

@vmk-dev running older versions of the Docker engine are not compatible with jammy-based containers.
This issue is caused because you don't have the latest docker version.
Please try to upgrade the docker to at least version 20.10.10 or add --security-opt seccomp=unconfined to the runner.
@myoung34 maybe you could add this info to README...

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants