Runner does not start anymore

Question

Runner does not start anymore

vmk-dev opened this issue 3 years ago · 4 comments

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?

Answer 1 · 2022-06-16T21:15:18.000Z

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

Answer 2 · 2022-06-16T21:27:08.000Z

Testing with 4064635

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

Answer 3 · 2022-06-17T16:30:30.000Z

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

Answer 4 · 2022-06-18T01:46:35.000Z

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