Replies: 2 comments 1 reply
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
|
reachability is fine. the runner process is choking on TLS trust/time, not “can’t talk to github”. that’s the catch - Set up job downloads actions with the runner (.NET), not with node. node/curl can succeed while the job setup path still fails. do this first on the same OCI container that runs jobs: date -u
# if this is behind "now", fix NTP / host clock first. a cert that starts at 00:00 GMT today will fail verification if the box is still on yesterday.
curl -fsS -o /dev/null -w '%{http_code}\n' \
https://codeload.github.com/ruby/setup-ruby/tar.gz/95ef2b042f9d7a56d8268cba8559e2842e2ad01b
# exercise the same stack the runner uses (if pwsh is there):
pwsh -NoProfile -Command \
"try { (Invoke-WebRequest -Uri 'https://codeload.github.com').StatusCode } catch { $_.Exception.Message; if ($_.Exception.InnerException) { $_.Exception.InnerException.Message } }"then refresh the image CA store and bounce the runner: # inside the runner image (debian/ubuntu based actions-runner)
sudo apt-get update
sudo apt-get install --reinstall -y ca-certificates
sudo update-ca-certificates
# and pull a fresh tag rather than a days-old local layer
docker pull ghcr.io/actions/actions-runner:2.337.0
# recreate the container / pod so it actually boots that layerif you’re on ARC, rebuild/roll the runner pods after the pull so they don’t keep an old rootfs. if that still fails
so: not “OCI can’t network”. it’s TLS trust/clock on the runner download path right after github’s |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Actions Runner
Discussion Details
Using
ghcr.io/actions/actions-runner:2.337.0The request status code is 200, and I don't think it's a network issue.
I don't know where this problem is coming from, because just 12 hours ago, it was still able to run workflow tasks normally, until today when he updated the certificate.
All reactions